It’s not game changing because someone else tried to do this and failed

Kind of a weird point to try and make no?

TBH I wouldn’t recommend you be building applications in .Net Framework… Most complaints about it have been a solved problem for years with .Net Core/.Net 5+. And there are upgrade paths, at least if you aren’t maintaining WPF/Winforms

Bugs and regressions? I wonder if that’s for different things than I touch, I’ve had almost no disruptions for the last 9 years. But I’ve mostly worked on console apps and backends. Almost no UI work aside from some WPF and Winforms side projects ages ago.

It’s been entirely open source for 7 years now…

Type system rigidity, I started using TypeScript a lot over the last few years with FE work. TS is so much more flexible and expressive. I really wish that I could express constraints in C# as fluently as I can in TS

Enums really need more flexibility, unions, discriminated unions, left hand implicit type, better value support…etc

System.Text.Json still sucks, it’s not greedy, no global setting , non-sane default,no expando support…etc it’s awful to use.

Unstructured data in general is an absolute pain to work with.

Composability of tests is still super painful and verbose. Dynamic test generation is awkward and unergonomic. After doing testing and other languages that let you simply compose tests imperatively, C# testing is definitely painful.

IMHO C# is an acceptable language with an absolutely fantastic framework.

I love C#, but these are my primary gripes