The Watercooler Squad is an important place for all things unimportant and nonsense at daily.dev. It’s designed to waste your time and distract you, buckle up 😻 🤹🏽‍♀️

Watercooler

The post includes an image related to JavaScript and Stranger Things.

Whyyy 😭😂

Because type coercion in JS complicated, just use === and save yourself the pain by eliminating it from the equation
I think it always tries to convert the value on the right to the same type as the one on the left.
So:
<ul>
<li>0 == “0” is truthy because it converts “0” to a number and it matches</li>
<li>0 == [] is truthy because when typecasting you’ll notice that Number([]) is 0 and so they match</li>
<li>“0” == [] is false because you removed the falsy value, “0” is not a boolean false like 0 is, but also, when it converts [] into a string, it becomes an empty string so you end up with “0” == “” which is false.</li>
</ul>

Thats why you should use === to compare the data type also with the value

comparing 0 to null is another story

this cause love and hate story with javascript 💔