In total. Just compare different web frameworks by performance, flexibility, features and so on. Whatever you compare, ASP.NET Core will probably end up in the top 20%.
People (particularly, HN) still associate it with the old .NET framework days and it being tied to Microsoft, Windows Server, etc.
.NET has had a hard time shaking off that old stigma, and to be fair, by the time it was really good, a lot of places already moved on to other tech (in particular, Go) .NET missed its window to escape the enterprise and despite being great, will probably never be seen as sexy.
I love it though. It's by far one of the most productive frameworks, and C# is pleasant to work with, and F# even more so.
Yeah it's lived experience vs perception for me. .NET developers have always, ALWAYS loved to tout how great things are but there's a reason anyone even slightly outside the MS-sphere simply chooses not to use it.
Because it's not that great, really.
The performance isn't that great in real-world scenarios (remember when they had to lie, in that "one" incident)? Even today the tests look NOTHING like actual idiomiatic .NET code.
Secondly, .NET developers tend to target a particular set of DevEx that I don't personally understand but that's not the problem, the problem is the DevEx has end-user effects; they simply just don't give a shit.
Anything past a simple B2B crud app in .NET is basically an uphill battle in real companies. It never works out, it's always more complicated than it needs to be.
But hey, no one gets fired for choosing MS. So here we are.
If you drop the religious zealotry, there's simply not a lot left.
It's been really great since I've been able to develop on Windows and deploy to a cheap Linux VM instead of having to deal with IIS. Game-changing for me.
The old asp.net was not only horrible in regard of deployment (iis/windows). The whole thing was a mess. It might've been innovative around 2005, but it was completely scrapped in ~2016 for a good reason.
