Technology

59549 readers

3333 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

1724

Microsoft Teams is dog shit (lemmy.world)

submitted 1 week ago* (last edited 1 week ago) by NegativeLookBehind@lemmy.world to c/technology@lemmy.world

496 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[–] Metju@lemmy.world 1 points 1 week ago (1 children)

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.world 1 points 1 week ago (1 children)

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.world 1 points 1 week 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