That’s all.

EDIT: Thank you all for detailing your experience with, and hatred for, this miserable product. Your display of solidarity is inspiring. Now, say it with me:

Fuck Microsoft

  • Valmond@lemmy.worldEnglish
    1·
    10 hours ago

    C# is such a crappy language.

    You can’t even do a=b if they are classes, and you’re forced down the chosen road all the time. It’s like java all over.

    • drake@lemmy.sdf.orgEnglish
      1·
      1 hour ago

      Sure you can, it’s the same in C# as it would be in C++ if you did a=b, where a and b are both pointers.

      You don’t want to copy the full data of a class around every time you use it, that would have extremely poor performance. If you do want that behaviour, use structs instead of classes. If you need to clone a class for whatever reason, you can do that too, but it’s not really something that you should need to do all that often.

      I don’t think you should really jump in and call something crappy if you just don’t really know how to use it, personally!

    • Metju@lemmy.worldEnglish
      1·
      10 hours ago

      And what would that equality entail? Reference equality? You have .Equals for that for every single class. Structural equality? You can write an operator for that (but yeah, there’s no structural equality out of the box for classes, that I have to concede).

      Hell, in newer C# (~3-4 versions back, I don’t recall off the top of my head) you have records, which actually do support that out of the box, with a lot more concise syntax to boot.

      As fir that being Java all over again: it started off as a Java clone, and later on moved in its own direction. It has similar-ish syntax, but that’s the extent of it.

      • Valmond@lemmy.worldEnglish
        1·
        10 hours ago

        It’s a single =

        a = 5;

        b = c;

        And hell, “use .Equal” is exactly what it is all about, have you heard of == ?

        Back in the day all the big languages were hard to learn and had lots of quirks, but somehow C/C++ moved on and became quite simple and elegant (you can write the worst trash with it ofc. but that’s like saying you shouldn’t cook because you might burn your chicken). C# not so much.

        • Metju@lemmy.worldEnglish
          1·
          3 hours ago
          • .Equals and == have different meaning in C#. Decent IDEs will warn you about that (and yes, that excludes Visual Studio, but that always was crap 😄).
          • As for (re)assignments - I don’t see an issue with that, tbh; you only have to be aware of whether you’re using a reference- or value type (and if you aren’t, then let’s be honest - you have bigger problems).

          I admit, “canonical C#” looks like shit due to a fuckton of legacy stuff. Fortunately, newer patterns solve that rather neatly and that started way back in C# 6 or 7 (with arrow functions / props and inlined outs).

          Tl;dr: check the new features, fiddle with the language yourself. Because hell, with ref structs you can make it behave like quasi-Rust

          • Valmond@lemmy.worldEnglish
            1·
            2 hours ago

            .Equals and == has different meanings? Like === in php or is it javascript 😅

            If you don’t see the problem with reassignment/pointer walking, then you are just too used to it to notice that it is total shit, how do you even copy the data from an instance of a class to another… Or are you “not supposed to do that”? If so, okay, but then c# is a ‘simple’ language, a script language like python or php.

            Also when you have a class A, make an instance isn’t:

            A a;

            I mean wtf…

            To each their own I guess :-) !