|
|
|
|
|
|
by xnorswap
47 days ago
|
|
|
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. |
|
|
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.