the problem i always had with dotnet was - why dotnet when java exists? then GO came to the party and completely deprecated both java/dotnet, at least to me,

the problem i always had with dotnet was - why dotnet when java exists? then GO came to the party and completely deprecated both java/dotnet, at least to me, i never looked back - native AOT compiled executable - 1 small file - ultra fast compile time - great ecosystem for all my backend needs, it's GO with dotnet everything feels heavy, ancient and bloated, msbuild and their xml for their projects, when you need to add some logic things becomes unreadable with XML logic, it's a mess, their json attempt wasn't great either, it was just JSON vs XML, they should have went with C#, build.cs, that's it then you have deployment, it's MUCH MUCH easier than with java and with their jar/classpath bullshit, but it still is a bloat, it's a DLL mess and let's not even talk about how everything is attached to microsoft even their WASM effort isn't called WASM, you can't target a WASM module, it's BLAZOR, with MONO (why mono still exist when you have dotnet core? i have no clue, it adds to the bloat sentiment), wether you like it or not, it's BLAZOR, wich sucks because i wan't to handle hosting my way, from the beginning they vendor lock you