This might be the most hilariously ridiculous true statement I've ever heard.
x == x _ is true. Good.
x == !x _ is also true. Oops?
And guess what:
Array(3)==",," _ is also true.
But
NaN == NaN _ is false.
Math.max()>Math.min() _ is also false!
but then again
Math.max()<Math.min() _ is true.
Madness, I tell you!
I asked a friend that does web dev and it is apparently pretty idiomatic JS. Pretty appalling. I finally understood why people claimed it was "hard to get right".
x === x; // false
"With a combination of large ground-based FORTRAN programs and small spacecraft-based assembly language programs, [Real Programmers] are able to do incredible feats of navigation and improvisation -- hitting ten-kilometer wide windows at Saturn after six years in space, repairing or bypassing damaged sensor platforms, radios, and batteries. Allegedly, one Real Programmer managed to tuck a pattern-matching program into a few hundred bytes of unused memory in a Voyager spacecraft that searched for, located, and photographed a new moon of Jupiter.
The current plan for the Galileo spacecraft is to use a gravity assist trajectory past Mars on the way to Jupiter. This trajectory passes within 80+/-3 kilometers of the surface of Mars. Nobody is going to trust a PASCAL program (or a PASCAL programmer) for navigation to these tolerances."
You would be better off asking him about the veracity of the stories.
I say this to hope you feel better at work. I've been pressed into frontend web work and it's fractal complexity.