And that doesn't even begin to touch on the absolute disaster of the net framework/core/standard/mono/uwp runtime situation.
C# as a language just doesn't seem very stable. I really don't enjoy using it anymore.
And that doesn't even begin to touch on the absolute disaster of the net framework/core/standard/mono/uwp runtime situation.
C# as a language just doesn't seem very stable. I really don't enjoy using it anymore.
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 :)
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"
(I can't justify why I feel that way. I have middleware-corporate-lang dysphoria for some reason.)