Most people do not even have a clue about which operating system their phone has. And they do not care. Just like they do not do with PC either.
If Windows Phone doesn't interest anyone. It is because they were unable to fit a niche. It is because their phone is a disaster. The operating system is irrelevant for most of phone users.
See, that's the problem. Someone says something nice about Windows and suddenly they're being told (in an incredibly fucking rude fashion) that they must be working for Microsoft because Microsoft is the devil.
You just proved his point that no one talks about Microsoft because of the social stigma attached to it. You just proved that if you say something nice about Microsoft, your peers will make you an outcast.
1) In mainstream use, Microsoft and Windows are 'Big Business'. Nobody wants that anywhere near the photos of their kids.
2) For geeks, Microsoft is the devil because they've managed to annoy most long time geeks in some form or another.
Indeed, it really is the problem. But it's the problem Microsoft is going to have to fix - and believe me, their 'spam the forums' and 'give free things' approach is not going to cut it. They need to drop the Windows and Microsoft branding for consumer devices in the same way Lexus is not Toyota. They need to make sure that the business and consumer products look as different as possible also.
I realize Microsoft is doing the exact opposite of what I've said above - and that's the real problem. What you're complaining about is just the mis-branding and mis-management of Microsoft bleeding through into the general populace.
In the same way that Android is a really decent Linux rebranding.
But I would ask that the platform be in some way open. Windows has always been open in that it will run on a variety of commodity hardware and there are no restrictions on who can develop for the platform and in how they can distribute their software. MacOS (and iOS) has always been restricted to Apple hardware. So Apple has always been more closed and walled garden-y than Microsoft with the exception that they use a load of open-source software in their OS stack once you look under the hood.
Microsoft (seeing as how they won't go the open-source model cuz it aint in their blood) could try and make the Windows Phone OS installable on a whole bunch of phones, it could allow for easy side-loading of apps and have a very low $ (perhaps even zero?) entry into their app store. That way Microsoft might eventually replicate the dominance they have on the desktop. But even then a lot of geeks are going to be wary.
Android really seems unstoppable. Nokia should never have gone exclusively with Windows Phone OS - it seems really strange back then and it seems practically suicidal now.
You know your text annoys me? Although the author is off the point, you continue the trend, and you're exactly as much correct as the author is.
Lisp syntax is just a notation for lists. Lisp implementations process those lists.
Any syntax which is a notation for something generic quite much makes sure that most changes into the compiler does not ripple into the parser. They make it easier to experiment with your compiler design because you're not changing parsing rules all the time. And changing parser code tends to be error prone and take lot of time, even when you're using parser generators.
I've found open source so liberating that I couldn't even consider closing down my source ever! For a while, for me, it's been morally wrong to close source code or rely on sources that's not within your reach.
"why should I compromise my own ability to license this and make some money from it?"
It's the same reasons you don't do slaves anymore. This guy needs to figure out better business models because the ones she's trying to do are obsoleted.
Also it's not wonder that her Kickstarter failed, it sucked very hard. Big TL;DR with no marketting material that would motivate people to pick on it. Most of people who saw that thing probably had no idea what they could do with her project.
Quick fix can be permanent fix. Those adjectives do not exclude each other out.
I think this article's biggest problem is that he's using running phrases too much, that are correct but without meaning: "If you skip work, you have to work more later" Obviously.
Also anything can be taken as art, even things not made by human! "Think of programming as an art". What does he mean?
This is your fifth top-level reply. It becomes a bit overwhelming when one person is the entire comment screen. Please, in the future, collect your thoughts and put them into one comment.
No, I don't think there is. They are all still broadly on the same topic. Imagine if I made each sentence here a separate reply. I mean, they are separate sentences and could conceivably be responded to individually, but it would still be pretty silly, wouldn't it?
The only case I can see for doing multiple sibling comments is if you have several truly unrelated thoughts that each deserve a deep treatment. But that's not what's going on here. As cheery noted elsewhere, he/she simply didn't know you could edit comments.
What's the point of having warnings in the first place, if you treat them as errors?
Also what's the point of having errors that prevent you from executing the rest of program? One error in one module shouldn't prevent huge suite from compiling.
If you stumble upon a new problem that's unknown to you, you should ALWAYS search what others have done. Only after that you'll try yourself if necessary, knowing the mistakes others made. Good programmers are lazy.
You won't challenge your mind any more by not searching, that way you're just being stupid. Besides, it's much easier to create original works if you know what's original and what's not. This is why you should be studying other's work before you do your own.
I've been always better off by starting with an empty file. It lets me concentrate on the problem I am solving, with no fringes or bells that belong to the finished product. Also starting from scratch is great if you're stuck. If something prevents this behavior, you're better off by tossing it away.
I think he should rather state to think clearly. You should always think for yourself about using a library. Does it fit your needs? Use it. If it doesn't, do not use it. You will not save time or your mind by using something that doesn't fit.
Copy-pasting code without understanding is functionally same as importing large libraries or linking to them. You'll have same problems even if you didn't copy anything! This is why good programmers review code and prefer open source.
His advice about copying is entirely wrong, because even if you don't understand some code, it can still be okay to use it in your project.
The biggest problem with copying is that you easily get more lines of code you have to maintain. This is especially bad if you copy large chunk of code, which may improve later. If that happen you have to do the copying again to get the improvements. Link or import the code you need instead!
Most people do not even have a clue about which operating system their phone has. And they do not care. Just like they do not do with PC either.
If Windows Phone doesn't interest anyone. It is because they were unable to fit a niche. It is because their phone is a disaster. The operating system is irrelevant for most of phone users.