Comment by tkubacki | Hacker News Reader

Comment by tkubacki | Hacker News Reader

I've quite unique experience beeing .net dev turning into jvm ecosystem. My decision to switch was based on fact that web is growing and .Net is simply...not fitting there.

Specifically what I mean is current VS is just not usable for web dev (comparing to Jetbrains tools), but what is even more important - there is nothing close to Spring Boot in terms of ecosystem richness (important for corpos) and even newest .net 5 is much more cumbersome compared to eg. golang (important for startups).

Don't get me wrong - I do like C# - it is a nice language (at some point it was better than Java), but current Java and other jvm langs and tooling (lombok) are great too or better (Kotlin) and current web/cloud ecosystem is all but not .net related.

if you develop for windows desktop or some .net oriented organization (some do politicall decisions) use .net, but if you can make your own decision and you develop for web/cloud just don't use .NET

> even newest .net 5 is much more cumbersome compared to eg. golang (important for startups).

FYI .NET 6 + C# 10 has a ton of work invested into removing the "enterprise boilerplate" experience and making the language and frameworks more akin to node or go in terms of effort/LoC required to spit out a program:

https://docs.microsoft.com/en-us/dotnet/core/tutorials/top-l...

There's also a few epics that are specifically focusing on .NET as a compelling cloud framework: https://github.com/dotnet/core/issues/5397

Still Visual Studio is simply broken compared to IntelliJ (especially for web dev) and there is not even a fraction of libs available for .NET compared to Spring Boot (take a look here: https://start.spring.io/)

We will see in 10 yrs if they catch up....

I have done both since they exist, alongside C++ and Web, and regardless of Microsoft tries to sell, UNIXy shops don't care about .NET Core.

Sure, C# is more pleasant to use than Java, and the language has almost C++ like capabilities for low level coding, but it lacks the 25 years of cross platform experience. And one can always include a native library if required, JNI might be boilerplate but it doesn't bite.

One cannot pick random .NET library and use it on .NET Core, most likely it is using .NET Framework APIs, COM or Win32 calls.

So already there, the ecosystem is reduced to the libraries whose authors have bothered to port to .NET Standard or Core.

Then issues like this, or how MAUI is being handled versus what Uno and Avalonia achieved on their own, show the ongoing power struggle.

From my experience, Go is much more boiler-plate-ish than C#. They wanted a very simple language with very simple libraries. But if the functionality is not builtin, you have to implement it yourself. Go is faster to learn but it will take more time to develop something.

Reply on news.ycombinator.com