Comment on Why Use Nim over C#?Comments−Idiot_in_Vain3yThere are literally millions of professional developers using C#. Any problem you run into has a solution documented online.Languages like Nim are a good choice for developers who need the adrenaline rush of dealing with complicated problems alone.−guilhas3yOne problem with the c#/dotnet ecosystem is there are too many answers online for different versionsc#, 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...−koenvdb3yMost of the time the answers are interchangable. There are a few exceptions but then you just look for "Specific problem .Net6" for example.−sebazzz3yI bet you I'll love any library in Node.js or the ecosystem itself. That's significantly worse.−rjh293yWhat is better, too many options or barely any?−guilhas3yFor an experienced c#/.net it is OK, but new developers might get confused and go learn another languageNim looks very clean. But I am not sure it is ready for complex production work−jackmott423yyou listed 3 versions of C# in that list, and they are all as similar as versions of any other language are.−silon423yIt's more or less true for Java... but in my experience, less true for c#.−oynqr3yDamn, didn't know C# can solve the halting problem.−osivat3yOf course it can, this simple feature has been in Visual Studio Enterprise for more than a year.
Comments
There are literally millions of professional developers using C#. Any problem you run into has a solution documented online.
Languages like Nim are a good choice for developers who need the adrenaline rush of dealing with complicated problems alone.
One 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...
Most of the time the answers are interchangable. There are a few exceptions but then you just look for "Specific problem .Net6" for example.
I bet you I'll love any library in Node.js or the ecosystem itself. That's significantly worse.
What is better, too many options or barely any?
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
you listed 3 versions of C# in that list, and they are all as similar as versions of any other language are.
It's more or less true for Java... but in my experience, less true for c#.
Damn, didn't know C# can solve the halting problem.
Of course it can, this simple feature has been in Visual Studio Enterprise for more than a year.