You misquoted me, I was saying that it is absurd to ask people to switch platforms on a whim. >Except that VS/C#/.NET isn't one of the best platforms around un

You misquoted me, I was saying that it is absurd to ask people to switch platforms on a whim. >Except that VS/C#/.NET isn't one of the best platforms around unless you code for Windows. And that's one more reason not to move to other platforms - because the tools they use don't support the alien technology as well as what they've been using. Code for Windows? As oppposed to what? Code for the Mac or Linux? These days most of the effort is in coding for the web. And it doesn't really really matter to the user if the website is running on Windows Server, Linux or BSD. >You obviously have a different idea of what constitutes a dead-end job. I imagine it's a job at a company that thinks of IT as a cost of doing business, something competitive advantages are not to be derived from. Those companies will not invest in new things until everybody eles is doing it. I've seen a lot of them. Sure there are, but if they ran on Ruby or PHP, they would be doing the exact same thing, I don't see how IIS is relevant here. The companies want a well supported product, with an available developer base and some of them choose the .NET stack based on MS' really long support cycles. >I know it's not a thorough review, but I see plenty of .asp URLs around within corporate confines. If you're seeing more ASP URLs than ASPX URLs, I would say your corporate selection is skewed. There have been and continues to be a massive number of migrations away from asp over the past ten years. Go compare the number of job listings on Dice for classic ASP developers vs. ASP.NET, it's not even a contest.