If it is the best option for you, then that's great - finding a good fit for your needs is what you should choose technology based on, after all. My own experie

If it is the best option for you, then that's great - finding a good fit for your needs is what you should choose technology based on, after all. My own experiences do not allow me to agree with all of your arguments, nor do I think you or anyone else can make them in such an absolute manner (such as about the language complexity/scope) but I also acknowledge that people will have different experiences, even with the same technologies! A trivial example of comparing the possible scope of any two languages in question, would be to glance at their lists of reserved words, for example https://go.dev/ref/spec#Keywords https://go.dev/ref/spec#Keywords and https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/keywords/ https://docs.microsoft.com/en-us/dotnet/csharp/language-refe... However admittedly that's not a discussion that I have the time for, though I'm sure that lots of people here might share their own thoughts and experiences. Honestly, for web development, everything starting with .NET Core and the newer versions has been pretty cool, so it's not like you have to deal with the inherent complexity every day, unless someone gets a bit too clever. Of course, less isn't always better, as certain other languages might demonstrate (a silly example, but still): https://en.wikipedia.org/wiki/Brainfuck https://en.wikipedia.org/wiki/Brainfuck The only thing I cannot agree with here strongly is your argument about Visual Studio: I yearn for the day when Microsoft will finally port it over to *nix, but if you don't need to support it as a developer platform then you're in a pretty nice place to be! For everyone else, in the mean time, I guess there is Rider https://www.jetbrains.com/rider/ https://www.jetbrains.com/rider/ (though, of course, a paid product)