Funny how your remarks are self contradictory. If you're writing in HTML and JavaScript, where do they run? Generally, that means an application server. But if you're writing standalone programs well yes they don't need an app server. But very few of us actually write stand alone apps that don't need some app server to run in.
Secondly, the point of bringing up Metro is the effect it will have on .NET, which means making it obsolete. In case you haven't noticed, nobody but MS is pushing .NET. So, if your primary champion gets on another horse, the future of .NET is not bright. Yes, everybody says they use the "best tool for the job" and that's why there are so many Scala jobs out there. That's why so many companies are clamoring to write SmallTalk apps. I worked for a big company in NYC that used Flex until we discovered it sucked and wasn't up to the task and then we switched our front end to Ruby on Rails which was awesome. So, I in no way am implying that Java is the only game in town. Instead, my point is that .NET is not a language with a bright future ahead--and that's why I would not recommend the used book store guy at the head of this article keep around a lot of old .NET books. Point made. Time for more Anonymous Cowards without the courage to write under their real handles to swarm.