I think its a naive attempt at describing worker processes and application scope. if you have a worker process per endpoint which is common with .net apps and lots of endpoints, its quite hard to balance resources. This is true. In PHP, none of this is of consequence.
Now I've got a tiny (280mb deployable, 5 hosts, 37 application pools, 5000 in flight requests 24/7) behemoth on my hands and I can testify its an arse pain to manage resources.
Th problem is whatever you do you're locked into an ecosystem of some sort. Even open source software. Have you tried building a portable c program on windows, Linux and OSX? Java is the least painless thing but we all know that's just another ecosystem.
The bit people forget is: stop procrastinating and build some shit.
To be honest, most people really don't give a shit. The next cigarette or pay day is far more important. Perhaps I'm getting old, but there are more important things to worry about.
Actually this is not true on windows phone 8 and windows RT. The only requirement is that you use the native API which means the browser back end will need to be ported to it.
Same thing, but I dislike Windows 8 in the same way I hated the bad bits of vista. I'll live with it if my ThinkPad dies big time though. The concept is really good but the execution is a bit clunky.
I'm quite happy with the tiles concept. In fact I'm typing this on a Lumia 820...
Windows Blue I imagine will iron out these issues. I have some hopes that it will be the next windows 7.