I wrote a blog post years ago on the subject of leaving .NET: https://blog.jonathanoliver.com/why-i-left-dot-net/ https://blog.jonathanoliver.com/why-i-left-dot

I wrote a blog post years ago on the subject of leaving .NET: https://blog.jonathanoliver.com/why-i-left-dot-net/ https://blog.jonathanoliver.com/why-i-left-dot-net/ My blog post got quite a bit of heat (both for and against). In the years that followed I actually had some discussions with a few of the higher ups within Microsoft regarding my blog post wherein they said they were very much aware of it and taking active measures to resolve the issues addressed therein. I am very happy to report that C# and .NET Core are very, very attractive options now. When I left (2012), I was sick of trying Linux .NET stuff (Mono) because I had to find/fix so many bugs and submit patches for it back to the mainline. Frankly, the Mono guys pulled off some miracles in my opinion but I kept getting bitten so much that I just couldn't use it. This was from about 2008-2012. Further, when I left and started using Go, on the techempower benchmarks (https://www.techempower.com/blog/ https://www.techempower.com/blog/) it showed .NET being almost dead last for HTTP requests per second. Nowadays Microsoft has pulled a virtually impossible feat of engineering to make their stack among the best of the best with regards to performance. In any case, Go is a solid choice. Where I work we are very, very happy with it. Every so often I miss some aspects of the syntactic sugar that C# had for things like LINQ, but on the whole I am very happy for the kinds of things I am trying to achieve in using Go. Further, the ecosystem and tooling are maturing nicely with a wide variety of libraries available. If I was to move over to a JVM-based language, I would consider Kotlin. If I wasn't using C# or Go or Kotlin, Rust is very high on my radar and continues to intrigue me.