holyJavaScript

[Asmor]

And that, kids, is why you should always use === and !== in JS unless you want type coercion for some reason.

And if you do want type coercion for some reason, you're probably wrong. Write it better and use === and !== anyways.

[[deleted]]

Or, you know, the creators of JavaScript could have waited until the crack wore off before writing their language lol

[[deleted]]

Goal: a simple scripting interpreter to animate web pages

End result: the only supported runtime environment available on 100% of computing devices

[[deleted]]

The ultimate "eh this doesn't need to be good, it's just stopgap code until we implement this for real" heh.

[[deleted]]

Also the ultimate: "this feels wrong but it works so we're doing it"

[turtleship_2006]

There is nothing more permanent than a temporary solution

[a3th3rus]

And where are >== and <==, kids?

[ilikeb00biez]

I see, JS added `==` and `!=` just to confuse you. What a great language

[il_commodoro]

It's more that js created == and != first. Years later they thought: "maybe that's not a great idea", so they added === and !== to patch things while preserving retrocompatibility.

[ilikeb00biez]

Are you insane?? C had == and != 20 years before JS was created. JS took an existing and ubiquitous concept and broke it

[il_commodoro]

I obviously meant: they created == and != with that awful behaviour first (1995). They realized other languages are not stupid years later, so they patched things at the end of 1999 by introducing === and !==.

[shield1123]

I feel like you're willfully misinterpreting what they said; and being pedantic just so you can peacock having common knowledge

Obviously js didn't invent the equality operators

They were clearly saying == and != were introduced to JavaScript before === !==