I’ve been wondering why not window.chrome == true or Boolean(window.chrome), but it turns out that the former doesn’t work and that == has essentially no use unless you remember some completely arbitrary rules, and that JS developers would complain that the latter is too long given the fact that I’ve seen javascript code using !0 for true and !1 for false, instead of just true and false because they can save 2 to 3 characters that way.
== has essentially no use unless you remember some completely arbitrary rules
If you make sure the types match, like by explicitly converting things on the same line on that example, then you can use it just like if it was ===.
In fact, there are people that defend that if your code behaves differently when you switch those two operators, your code is wrong. (Personally, I defend that JS it a pile of dogshit, and you should avoid going to dig there.)
I’ve been wondering why not
window.chrome == trueorBoolean(window.chrome), but it turns out that the former doesn’t work and that==has essentially no use unless you remember some completely arbitrary rules, and that JS developers would complain that the latter is too long given the fact that I’ve seen javascript code using!0for true and!1for false, instead of justtrueandfalsebecause they can save 2 to 3 characters that way.If you make sure the types match, like by explicitly converting things on the same line on that example, then you can use it just like if it was
===.In fact, there are people that defend that if your code behaves differently when you switch those two operators, your code is wrong. (Personally, I defend that JS it a pile of dogshit, and you should avoid going to dig there.)
I’ve never seen the
!0and!1, it is dumb and indicates either young or terrible devs.Boolean(window.chrome)is the best,!!window.chromeis good, no need to test if it’s equal totrueif you make it a boolean beforehand.i just added the
=== truefor clarity