3 ms·
> C# as a language just doesn't seem very stable In what way do you think it isn't stable? I've upgraded code written in C# v1 to the latest and greatest and n
by teh_klev 4y ago
> C# as a language just doesn't seem very stable
In what way do you think it isn't stable? I've upgraded code written in C# v1 to the latest and greatest and never had a breaking change (well except for one time where it was my own fault for abusing reflection).
Ultimately you can use as much of the language as you want to, the "old" ways haven't been removed and you can still code like it's 2002 :)
- rolenthedeep 4y agoI'm aware that I'm yelling at a cloud, but what really did it for me was nullable reference types. I get it, I understand why nulls are a problem and how annoying they can be. I've done my time in the trenches tracing nullrefs in production. But I just really, strongly dislike the way Microsoft went with the problem. Declaring types nullable with the `?` just puts me off. `Nullable<T>` was always something to be avoided, and I find the syntax just as annoying as null checks. Ultimately most of my complaints can be boiled down to "too much changed and now things are different"