3 ms·
It's the opposite for me. C# is becoming a complete clusterfuck of half baked features, bad historical choices, fear from Microsoft product owners to clean up t
by dustinmoris 4y ago
It's the opposite for me. C# is becoming a complete clusterfuck of half baked features, bad historical choices, fear from Microsoft product owners to clean up the language and deprecate some old shit that is just polluting the language and making it hard for new beginners to learn and the worst of all, C# has a huge identity crisis and it shows in the yearly updates. The language changes so much every year that it's too tiresome to keep up with, it's increasingly more confusing and it is very unclear if C# wants to be an OOP language, an FP language or some weird jack of all trades. It's a horrible choice for beginners and I have seen many newbies who absolutely got frustrated by C#.
Go is very neat, true to its core identity and very very stable. I have been developing .NET (C# and F#) for almost 20 years and I don't enjoy it at all anymore.
EDIT:
Just last week the .NET team tweeted that they are looking to introduce green threads to .NET after all. I love the green thread implementation in Go and I think it is superior to .NET's async/await model which get scheduled by OS threads, but .NET has gone down that route many years ago and it's embedded everywhere now and introducing such a new fundamental change now is just plain fucking stupid. Microsoft is so dumb for even thinking this is a good thing to do. If they don't like how C# works then invent a new language with modern fundamentals which you like but stop changing C# so much that it's become completely unrecognisable. .NET developers don't want to rewrite their code bases every 12 months. We have real work to do.