this post was submitted on 13 Nov 2024
1695 points (96.1% liked)
Technology
59370 readers
3921 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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!
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
And what would that equality entail? Reference equality? You have
.Equalsfor 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.
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.
.Equalsand==have different meaning in C#. Decent IDEs will warn you about that (and yes, that excludes Visual Studio, but that always was crap 😄).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.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 :-) !