4 ms·

I have the same issues with C#. I came up in the days of .net 4.5, in the years since I've watched Microsoft bolt an entire language worth of features on top of

I have the same issues with C#. I came up in the days of .net 4.5, in the years since I've watched Microsoft bolt an entire language worth of features on top of C#. I didn't use the language for the last five or so years, and I feel so lost that I avoid using it now. 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.

shrimp_emoji 4y ago
That anyone could ever have enjoyed Microsoft Java seems crazy to me. :p (I can't justify why I feel that way. I have middleware-corporate-lang dysphoria for some reason.)
kmac_ 4y ago
I have quite opposite opinion. Every extension increased readibilty and cut the cruft. For example, even simple changes, like native tuples or expression bodied members tremendously changed how the language should be used and how the "correct" code looks.
- metaltyphoon 4y ago
  Agreed, C# was too verbose and its way less now.
  - programmer_dude 4y ago
    C# syntax is gradually approaching F#. I'd say just use F# and skip the bloat.
    - GiorgioG 4y ago
      Maybe if Microsoft bothered to invest in and promote F#.
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 ago
  I'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"

shrimp_emoji 4y ago

That anyone could ever have enjoyed Microsoft Java seems crazy to me. :p (I can't justify why I feel that way. I have middleware-corporate-lang dysphoria for some reason.)

kmac_ 4y ago

I have quite opposite opinion. Every extension increased readibilty and cut the cruft. For example, even simple changes, like native tuples or expression bodied members tremendously changed how the language should be used and how the "correct" code looks.

metaltyphoon 4y ago
Agreed, C# was too verbose and its way less now.
- programmer_dude 4y ago
  C# syntax is gradually approaching F#. I'd say just use F# and skip the bloat.
  - GiorgioG 4y ago
    Maybe if Microsoft bothered to invest in and promote F#.

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 ago
I'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"