@electrineer "We have invested so much time and money into the servers and infrastructure to make this notification service possible. There is no fucking way that we won’t force it down the throat of our users by making it opt-in"

@electrineer and naturally MS assumed that the majority of users would be like that and made it enabled by default.

@Demolishun a true villain doesn’t want to just kill everyone. A much more evil plan would be to control everyone via microchips. Those chips could be injected together which "medicine" or something like… vaccines. I don’t know, just some ideas.

I suppose those are unisex

Those emails are useless anyway because whenever I’m online to see the email, I’m also online to see the notification in Teams.

Since they don’t work reliably anyways, it’s a no brainer to disable them.

@electrineer I’ve disabled them now, too.

I wonder what would happen if we trained a LLM exclusively with kiki dreams.

@devJs FF8 ❤️

The lack of trying to convince it disturbs me.

The Gray War was fought by black and white people, hence the name Gray.

@lorentz right. There was too few context to see if the returned null was legitimate. I assumed that it was just about the forgotten comment :)

@lorentz yes, because this "bug" has nothing to do with dynamic typing ^^

@jestdotty you quoted me wrongly and inserted a few words which change the meaning. I believe you misread or misunderstood me.

My point wasn’t about performance. It was about verbosity and correctness.

I don’t want to insult you. You insult yourself by confirming my prejudices about js devs.
It may not be your first language but it is your main language that you also like. So it’s appropriate to refer to you as a typical js dev.

Prost!

@kobenz readability is much better as well. See my example with Swift.

@jestdotty what a strange question.

You need to check objects for equality to check if some data has changed. That’s essential for reactive and functional programming.

But I think I can see why js devs don’t recognize this problem because js doesn’t have custom value types, and changes in state are handled with reference types. That’s bad because you need to deal with mutable state but there is no other way of course.

That’s the problem with js: It makes you blind for its problems because you never learn good coding practices because they are not possible with js.

Well, it’s already accepted that people can demand to have whatever ridiculous pronouns that they want, so demanding to be treaded as a pregnant male suddenly seems less stupid in comparison.

@devJs In soviet russia, we stab with rifle and shoot with knife!

@Demolishun I need to remember that term douche nozzle. It sounds like a funny and obscure alternative for dumb fuck.

Happens to the best.

@Demolishun exactly! 👌

@retoor me too but spammers aren’t here to answer questions, unfortunately

I heard something similar from the tv series Dexter, that I binge watched recently:

"I have always maintained that the greatest obstacle in life isn’t danger, it’s boredom. The battle against it is responsible for most of the events in the world, good or ill."

@jestdotty show me the code to check two arrays or two arbitrary objects for equality in js.

In Swift, you just conform the object to Equatable and then compare with ==. Arrays do conform to Equatable automatically if the element type is also Equatable. I bet my ass that Rust does the same.

Now tell me which is more verbose.

All that === does is skipping the retarded implicit conversions. It still is a joke of an equality operator which doesn‘t work with reference typed values like arrays and objects, as I said. The type system is still garbage.

constructively dismissed?

@devRancid Btw, js doesn’t have a built in way to check for equality for reference typed values. == and === will both not work.
So two equal objects and two equal arrays would still be unequal according to == and ===.
The type system is garbage.

@devRancid … which is a testament to its fucked up type system in itself.
Not using it because it’s bad is admitting that it’s bad.

@jestdotty https://dorey.github.io/JavaScript-...

Implicit type conversions when using ==

Death by light saber, wielded by a tiger wearing sunglasses.

@cuddlyogre that’s exactly the reason why a well thought out and properly implemented type system is one of the most crucial parts of a programming language. Without that, we get those clown languages like php or js, which have random conversion rules between built in types, which were implemented for some irrelevant use case at the beginning and then stay forever in the language because of backwards compatibility.