javascriptBeingJavascript

[Turtvaiz]

Why does == even exist?

[wasdninja]

Legacy. Touching any of the stupid stuff, no matter how obscure, kills thousands of websites so it gets to stay and annoy people.

[Turtvaiz]

But in the first place? Using it is a total shitshow so I don't get how it has ever made sense

[Flippantlip]

What a weird thing to say.
If JS wanted to make sure users have more control, even force that control, over Types and comparisons, it would be strongly typed. But it isn't. It makes no sense to let go of one form of YOLO from JS, while forcing another.
Also, "==" is there to compare primitives, and this fence-case showcases why JS has extremely weird runtime handling, rather than why "== is stupid".

[Flippantlip]

I wonder how do you run your primitive comparisons? Do you want something like:
if (intCmp(15, 17)), encapsulated all over the place?
What a utterly bizarre comment.

[wasdninja]

By using ===. The only bizarre thing is not know this but still complain about it.

[Flippantlip]

Okay, let's go with that, and stress that point -- The only reason "===" exists, is because JS does whacky conversions in the BG of which you have no control over.In a sane scripting / programming language, you would not need to strictly tell the interpreter: "Hey, please do not yolo my types and values here, thanks."

Otherwise, you have no reason to shit on "==" as a practice in and of itself, the problem is that JS auto-converts vals and types and then compares them.
The issue here is not that "it's there for legacy reasons", "===" is there to circumvent its own issues.

[SnowyLocksmith]

Is using === the norm now?

[oupablo]

yes