Except strict equality, that’s a JavaScript only problem. Imagine thinking "0" should be falsy in comparison due to string literal evaluation, but truthy with logical not applied based on non-empty string. Thus !"0"=="0" is true. They couldn’t just throw away == and start over nooooo let’s add === . Utter madness
Except strict equality, that’s a JavaScript only problem. Imagine thinking
"0"
should be falsy in comparison due to string literal evaluation, but truthy with logical not applied based on non-empty string. Thus!"0"=="0"
is true. They couldn’t just throw away==
and start over nooooo let’s add===
. Utter madness