There's a pretty big difference here: lack of choice. If you want to deploy native apps to iOS, you literally have no choice but to get into that world. If you want to deploy web applications (as many startups, especially HN startups do) there are dozens of options to choose from aside from buying into a single vendor's full stack.
Just look at Silverlight. Who wants to install that on their Apple or Google device? Flash is bad enough. And yet it's what Microsoft wants you to use to make your ASP.Net app have fancy graphs. L-L-L-lock-in.
Even iOS and Android wouldn't be as powerful as they are had fully-interoperable webservices not come first (killer apps like Gmail, Twitter, Facebook, and Dropbox are webservices first, apps second. You can't compete with them by making an app first, they're platform agnostic.)
So yeah, given the chance Microsoft will try and make Windows 7 running IE accessing a Windows 2008 Server running a .Net app on IIS with a MS-SQL Enterprise backend the only option. It's a testament to the fierceness of the FOSS and LAMP communities that Microsoft is losing this battle (and the world is better off because of it.)
As far as backend development is concerned. You have to buy the tool chain as well as the software(read OS, SQL Server, IIS etc etc) for the servers that your developed software runs on. Now the problem comes when you need scalability. Adding more servers to your stack means not just spending money on hardware but on the software stack as well.
So now it all boils down to buying real large and powerful servers since scaling out is not cheap. This has added risks like on issues like replication, back up etc etc.
No one wants to be caught up in this sort of a situation. Especially start ups.
It is a mobile tool chain. You don't need to use Macs for servers... (And the cost of an iPad, iPhone and iPod touch isn't high. You will need a phone anyway. And iPad is the only real game in town for pads, so you'll probably buy one anyway.)
The notion that every dev getting into the iOS space was converting from Windows at an enormous upfront cost seems rather daft. OS X had a lot of dev traction before iOS existed.
On the web side, I really think cost is the driving factor more than anything. As long as there's a free (open source) solution to MS's framework that is on par (we can argue either way which frameworks/platforms are better) there's little incentive for startups to go .NET. If a LAMP stack started costing as much as a .NET stack the landscape would be very different. .NET faces the problems going against the Java stack.
In the end, it's about the money. Which platform can I make more money on and does it more than pay for the costs to be on the platform? Right now on mobile it's iOS and on the web it's typically LAMP or lately a Ruby on Rails stack.