3 ms·
C# is still very much a decent language, but it's not as shiny as it used to be. I have worked professionally with .NET and C# since the 1.0beta and I have to
by alkonaut 8y ago
C# is still very much a decent language, but it's not as shiny as it used to be.
I have worked professionally with .NET and C# since the 1.0beta and I have to agree: it's not that good any more. Not because it's gained so much bloat or because it has gotten worse, but because its ecosystem has been fractured so many times I stopped counting. The core ordeal is just the last in a series of disruptions and the previous one was Roslyn. These aren't bad initiatives, it's just that they aren't ready. Roslyn is barely working in VS together with the project system (which is odd given it was shipped first in VS2015)! I applaud ms for developing more in the open, but the constant renaming and churn of everything is tiring.
But all that aside, C# is still decent, the only thing making it less shiny now is that we realized that OO is a promise that didn't deliver. I don't want to program another line without proper algebraic types for example - yet here we are.
- eksemplar 8y agoI’m not sure who’s downvoting you, but it sure isn’t managers who’s paid for people getting re-educated in asp, then mvc and razor, then web-api, then xamarin, then core 1, then core 2 and that’s just to name a few. Hell, it’s still not easy for people to deploy a .net core web api and run it in an IIS installed with basic settings. You can laugh at it, but that’s 80% of the damn workforce who doesn’t know how to do that. I mean, the JS environment changes, but I haven’t had to pay for anyone getting reschooled since we swapped to JS.