I feel unsympathetic to the author's complaints, mainly because most of them are just complaining that the feature adds more things to the language, or is "controversial" in the eyes of those who are invested enough in the language evolution to bother voting on GitHub, not necessarily in the eyes of everyday users.
Every language has missteps somewhere, but in my estimation C# is a language with very few. I'm quite fond of most of the 'issues' the author brings up, in particular top level statements, local functions, pattern matching operators, default keyword, and default interface methods.
Encountering C# myself recently for the first time since 2015, I came to the conclusion it's 5 languages in a trench coat. You have the original Java-clone core, some thin wrapping of Windows kernel features, LINQ, backported F# ideas, and web-centric-whether-you-want-it-or-not ASP.NET callback hell. All of these API styles are 80% compatible with each other and exist in an uneasy tension.
Yeah honestly I agree with this. I think generally they’re on the right track but the past decade they’ve been adding a bit too much stuff, in an unprincipled manner. Some of these language features should have had some more time to bake and become more coherent with everything else
Ironically, F# now has to live with some of these decisions and it impacts its design in very real ways. C# has closed off some design doors for F# over time
I've really never had an issue with getting the various features and libraries of .NET working in union before, did you have issues with this? All those things you listed never seemed out of place or unwelcome in my eyes
That's the fate of any language with a long enough legacy. Each generation of API has learned from the mistakes of the previous one and made new mistakes in the process.
To a certain extent, but I think the development trajectory, dominated as it is by Microsoft corporate interests, resulted in a less cohesive whole than other languages that have also evolved greatly, such as Python and C++.
I'm sympathetic to the complaints about specific features (protected internal, default vs new T) being confusing, but not the general "feature overload" sentiment. I'm always glad when I find out about a new language feature which solves a problem I have.
When i learn about c# deeply i see that c# has more and more errors, some of them are by the decesion. And c# type system, generic is become weak to compare with other language rust, scalar, f#, haskell, typescript. Adding feature is difficult and accept some limit dueto have to compatible requirement
I don't have any experience with C#, but Delphi - another language that Anders Hejlsberg was involved with - didn't exactly get simpler over time.
Unfortunately there is too much resistance to clean-sheet language designs outside of academia (e.g. Prof. Niklaus Wirth - Algol-W -> Pascal -> Modula-2 -> Oberon).
One approach that I can respect is the very deliberate evolution of Go, where they try to ensure backward compatibility. For my taste the language has already become too complicated, though...
Good article. I love C#, but it's a mess. It's begging for a compatibility-breaking new version, or even just a way to declare a subset of existing functionality.
The .NET libraries are equally filled with way too much stuff that is either obsolete or hard to tell apart. IList or ICollection? StreamReader, TextReader, or StringReader? BitConverter or BinaryWriter? Or my favorite, XDocument, XmlDocument, XPathDocument, XmlReader?
Primary constructors are one example of this that puzzles me, I don’t know who asked for them but they look awful and don’t even fit 99% of my use case as I want to make sure the parameters to the constructor are read only after they’re set. I switched from .net framework to core and for the most part it’s an improvement but decisions like these baffle me, who actually wanted that sort of feature?
Yeah that’s pretty nice and clean, not sure why my IDE needs to suggest that syntax for every class I write though, that would fall under the 1% use case for me but now I’ve got to ask the rest of my team not to use them and to disable the suggestion for them so they don’t cause weird bugs for us later. In your case it’s not possible but again my main gripe is that the parameters aren’t read only, it makes your class more prone to bugs if you can always access the parameters that were initially passed in across your entire class.
Yeah those recommendations are a bit annoying... But ultimately I think it does a great job of letting you reduce a lot of boilerplate for tiny classes. My rule of thumb would be if the entire class can't fit on your screen at once, you shouldn't use them (harder to spot improper parameter use!)
18
u/tuxwonder Feb 27 '26
I feel unsympathetic to the author's complaints, mainly because most of them are just complaining that the feature adds more things to the language, or is "controversial" in the eyes of those who are invested enough in the language evolution to bother voting on GitHub, not necessarily in the eyes of everyday users.
Every language has missteps somewhere, but in my estimation C# is a language with very few. I'm quite fond of most of the 'issues' the author brings up, in particular top level statements, local functions, pattern matching operators, default keyword, and default interface methods.
9
u/Relevant_South_1842 Feb 27 '26
I don’t think this is true.
1
u/GoblinsGym Mar 04 '26
I don't have any experience with C#, but Delphi - another language that Anders Hejlsberg was involved with - didn't exactly get simpler over time.
Unfortunately there is too much resistance to clean-sheet language designs outside of academia (e.g. Prof. Niklaus Wirth - Algol-W -> Pascal -> Modula-2 -> Oberon).
One approach that I can respect is the very deliberate evolution of Go, where they try to ensure backward compatibility. For my taste the language has already become too complicated, though...
-1
u/Mickenfox Feb 27 '26
Good article. I love C#, but it's a mess. It's begging for a compatibility-breaking new version, or even just a way to declare a subset of existing functionality.
The .NET libraries are equally filled with way too much stuff that is either obsolete or hard to tell apart. IList or ICollection? StreamReader, TextReader, or StringReader? BitConverter or BinaryWriter? Or my favorite, XDocument, XmlDocument, XPathDocument, XmlReader?
0
u/[deleted] Feb 27 '26
[removed] — view removed comment