3 ms·
I wonder if we are not close to the end of C#’s useful life. It’s a great language but it has become so convoluted with dozens of way to do the same thing, larg
by cm2187 9y ago
I wonder if we are not close to the end of C#’s useful life. It’s a great language but it has become so convoluted with dozens of way to do the same thing, largely due to improvement that came along the way. Like methods accepting objects coexisting along methods accepting generics. Old async syntax (callbacks) along task async, like out and ref parameters now that we have valuetuples, etc. I wonder if .net core isn’t a missed opportunity to clean up the language.
- dtech 9y agoIf .net broke backwards compatibility it would be even harder for it to gain traction. See python 2 -> 3 etc.
- cm2187 9y agoBut at the risk of being overshadowed by a newer, simpler language. Which is kind of what is happening now with python (it's not newer but its simplicity is giving it a lot of traction).
- helthanatos 9y agoThere's a risk of being confused on how to do things with backwards compatiblity, but it's something that makes me like c# better than other languages. Being able to add new features without removing old features is great. Older examples of c# may look completely different than new examples but that is great because someone can continue without learning all the new stuff (kind of odd, but eh). Removing old functionality could doom them because they already have a lot of confusing dependencies when using part .net core, part .net 4.5. They don't support newer versions of .net on the old windows 10 versions, making support complete Hell as far as that is concerned. I think cleaning up documentation and old examples some would make the evolution of the language easier but isn't strictly necessary to still be useful. Even in strict enterprise, though it may be annoying.
- fauigerzigerk 9y agoI think C# is lucky in a way. It's getting old and bloated at a moment in history when modern is essentially synonymous with being a convoluted multi-paradigm monster gobbling up features and syntactic sugar at a frantic pace. Even the Go crowd has made the first step towards quantum computing, leaving behind errno in favor of returning both a possibly invalid return value and an error that can be nil and non-nil at the same time! ;-)
- mercer 9y agothat last bit sounds terrifying.
- gregmac 9y agoI think the opposite is true. First, the backwards compatibility is a key feature. You can open a project written several years ago, and add a new feature to it using the latest language syntax without being forced to rewrite all the old code. I'm not quite sure about stock visual studio (since I don't use it), but Resharper (and their new Rider IDE, which I've played with a bit) is pretty good at highlighting code doing things the old way and even automatically rewriting it for you. This seems to be getting better as they take advantage of what the Roslyn compiler can help with. .NET Core, native, and the work of Xamarin only means more cross platform support, which allows broader use beyond just the Windows world. The ecosystem is starting to get caught up now, and between most popular libraries being available and the feature parity reached with .NET Core 2.0, things are looking great for it to grow even more popular.