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

  • @[email protected]English
    1•9 hours 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!

    • @ValmondEnglish
      1•6 hours ago

      In C++ you have the choice, the compiler makes the shallow copy (you know what that is right?) automatically if needed, or you can move around the pointer or a ref. Or, transform the shallow copy into a deep copy if you need that.

      In c# you don’t even not have the choice, ints etc gets copied but classes aren’t. Where’s the logic behind that?

      And as so many others you scramble to find some excuse that “you should probably not do that very often anyways” or some other bullshit.

      I heard all that 20 years ago when it actually had some merit for people trying to run it on the old crappy hardware of the day, today it’s just moot.

      Need speed or low memory usage? Learn to code in C/C++ for example. Heard Rust is great too.

      C# is just an old wonky language.

      /Rant off