I've been a .NET developer for close to 10 years. Our last product (UsabilityHub.com) was written in .NET simply because it is what I know.
In reality it doesn't matter how good .NET is, there are two reasons why we didn't use it for our latest venture (BugHerd.com).
1) .NET is always one step behind. When people say .NET for web apps, they really mean MVC. I love it, but the reality is that it's a .NET implementation of what was long since done elsewhere. .NET will always be a step behind. Although I must say, sometimes being the second to implement something is a good thing for stability.
2) Hiring .NET developers means hiring enterprise developers. A huge generalisation here, but that means engineers that have worked in big teams under constant direction. They don't do open source, they don't read other people's code and they aren't used to working autonomously.
In reality it doesn't matter how good .NET is, there are two reasons why we didn't use it for our latest venture (BugHerd.com).
1) .NET is always one step behind. When people say .NET for web apps, they really mean MVC. I love it, but the reality is that it's a .NET implementation of what was long since done elsewhere. .NET will always be a step behind. Although I must say, sometimes being the second to implement something is a good thing for stability.
2) Hiring .NET developers means hiring enterprise developers. A huge generalisation here, but that means engineers that have worked in big teams under constant direction. They don't do open source, they don't read other people's code and they aren't used to working autonomously.