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.
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...
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.
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
I bet you I'll love any library in Node.js or the ecosystem itself. That's significantly worse.
Languages like Nim are a good choice for developers who need the adrenaline rush of dealing with complicated problems alone.