News for hackers. Stuff that matters.
Re:Why Use Nim over C#? by guilhas on Wednesday March 01, 2023 @06:03AM (#34981001)
The problem with the c#/dotnet ecosystem is there are too many answers online for different versions

c#, records, EF6, EF core, EF7, net4.8, net standard, net core, net6, webforms, blazor, web api, web mvc, razor, identity core, legacy, UI, dotnet cli, visual studio, vscode, nuget, CMD, powershell...

Re:Why Use Nim over C#? by koenvdb on Wednesday March 01, 2023 @06:14AM (#34981078)
Most of the time the answers are interchangable. There are a few exceptions but then you just look for "Specific problem .Net6" for example.
Re:Why Use Nim over C#? by jackmott42 on Wednesday March 01, 2023 @06:30AM (#34981164)
you listed 3 versions of C# in that list, and they are all as similar as versions of any other language are.
Re:Why Use Nim over C#? by rjh29 on Wednesday March 01, 2023 @06:11AM (#34981052)
What is better, too many options or barely any?
Re:Why Use Nim over C#? by guilhas on Wednesday March 01, 2023 @12:15PM (#34984993)
For an experienced c#/.net it is OK, but new developers might get confused and go learn another language

Nim looks very clean. But I am not sure it is ready for complex production work

Re:Why Use Nim over C#? by sebazzz on Wednesday March 01, 2023 @10:13AM (#34983233)
I bet you I'll love any library in Node.js or the ecosystem itself. That's significantly worse.