> tech made for large slow enterprise teams. This is complete nonsense. It is popular nonsense, but nonsense nonetheless. .NET is a perfectly reasonable tech

> tech made for large slow enterprise teams. This is complete nonsense. It is popular nonsense, but nonsense nonetheless. .NET is a perfectly reasonable tech stack for certain kinds of problems -- for example if your application has to interact regularly with MSFT core APIs, you'd have to have a pretty compelling reason NOT to use the MSFT-native stack. > It all relates to the enterprise vs hacker mentality This too is a story that HN likes to tell itself to justify its preference for this week's hot new javascript framework (or whatever). At the end of the day, different tools are good for different use cases -- and while yes, .NET tends to work better when you're coding to "enterprisey" use cases, that doesn't mean that your product team itself has to operate in a "large slow enterprise" way (Plug: If you're a top notch .NET developer and you want to work with others who are as well, at a place that doesn't treat C# and .NET as second class citizens, hey, drop me a line.)