[2ndorderthought]

The .net sdk is like 1gb, go is like 60mb or something. It's annoying when that matters.

More so, nothing happens quickly with it's tooling, and the tooling isn't friendly. All of a sudden I can't build my project in vsstudio(also bloated but admittedly optional but may be required depending on where you work). Clean build also fails. So I have to go to the command line and type in dotnet restore, dotnet build, magic it works now. ???

Okay time to install a package because msft has its own packages for things like aspnet but now I want to serialize json. Cool newton soft sounds good. Ah now I need a package manager, I'll install nuget. Oops I need to tweak this weird xml file with lots of options.

I press compile I wait 3 minutes to realize there is an error. Okay it builds and looks good in debug mide now I want to send my application to a friend who doesn't have .net runtime...

With go it's more like. Okay I automatically have web access from the std lib. I want a framework oh I already have a package manager. Edit my toml. One command done. Time to compile, poof done in 2 seconds. I send the binary to my friend and they run it.

I understand some of these are 1 time cost things, but I am requesting you to read between the lines as these aren't examples I am trying to quibble over. The point is the friction that go has focused on removing by being quick and small. It has less legacy cruft but I tried to ignore as much of that as I could.

Also keep in mind j am not a big go fan. It's not my favorite language but it is way easier to deal with on a regular basis for me

[xnorswap]

That's quite a rant, but it seems like it's from experience with the old times. For the last decade or so it's been a completely different story.

System.Text.Json is part of the core standard library, the only reason to use Newtonsoft is developing on legacy applications.

Visual Studio isn't necessary or even much recommended any more. VSCode or any LSP editor works fine.

You don't need to install nuget, any more than you need to install cargo in rust, it's part of the SDK. You can also just edit the csproj in the same way you could edit your TOML file. It's XML, and you just add <PackageReference="" />.

You can compile --self-contained to be able to run it somewhere without the runtime installed.

.NET has a long history, but almost none of these are actual points of friction in the current year.

[2ndorderthought]

I disagree as someone who was using dotnet within the last 2 years.

Also we are comparing go to .net not to rust. Go is much easier and faster tooling wise. It doesn't require an IL and doesn't have 2 decades of enterprise cruft with vendor lock in strategies baked into it.

I asked to read between the lines.

The experience behind each of these things really stinks compared to go. If you haven't tried it, I recommend it just to feel the ergonomics. I don't care for go as a language. The funny thing is, I find the tooling so much easier, better, faster than .net that even though I like c# more than go as a language, I would prefer to start a new project in go instead of say c# instead. It's that annoying for me. I've met several other people who are language ambivalent who feel the same way.

I could write a huge blog post about it with facts. I'd rather not though. People do what they like and I am not here to change what someone likes.

[shynome]

.NET is too slow to use in my pc