|
> I'm not sure why there isn't more momentum towards using .NET. I've thought about this too. Although I've done DotNet since 2001 I'm not blind to the faults; I also do Go, Node, Ruby, Python, and PHP. What I've concluded (and I could be wrong) is that as powerful as DotNet is it is held back, understandably, by the Windows-centric nature of the original .NET Framework (ending at v4). Unless an open-minded assessment is done, that (fair) bias means that it isn't really taken seriously outside of enterprise. Which is a shame as it is (to within a degree that makes the difference irrelevant) as productive as Rails, as powerful as Java, as performant as Go, and as easy to read (when written well) as Python or Ruby. Coupled with the fact that it is now cross-platform with self-contained and trimmed single binaries, it really is a shame. I still remember the first thing that got me looking at Ruby was actually Rails, and it was doing the 15 minute build-a-blog tutorials. Nowadays with EF Core, DotNet 6, Postgres, migrations, and scaffolding, it is almost as fast in DotNet. And the result is a type-safe codebase that requires massively less resources to scale. |