> Unfortunately, the .NET 6.0 implementation turned out to be problematic for some users: a failing connection attempt also fails the request on the top of the request queue, which may lead to unexpected request failures in certain scenarios.
Good reason to upgrade
C# was my first programming language, and it's always been the first thing I reach for to knock out a quick program, but I find myself using it less and less these days.
The new language features are neat, I guess, but a lot of it feels like bloat. And then there's the absolute trainwreck of the framework, core, standard, mono, and wpf ecosystems.
There's also a general distaste for Microsoft lately. I tried to open one of their sample projects to figure out Bluetooth, but it told me I had to upgrade to windows 11 to compile it.
Today I built a one screen ui with wpf. There are exactly two textboxes, three checkboxes, a combobox, and a button. 200 lines of code at absolute maximum. I tried to build it as a single executable, and it produced a 140MB file that doesn't work without some mysterious dlls in the same directory. Kind of the opposite of "output single file" imo.
The whole dotnet ecosystem has become so bloated and problematic that it's just not worth the effort to use it unless I have to.
And don't get me started on AppDomains or assembly loading. I discovered a bug in there years ago and I'm still mad about how much trouble it caused me.