1527
"Works for me" (lemmy.sdf.org)
submitted 2 years ago by to c/programmer_humor@programming.dev
83 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 18 points 2 years ago (7 children)

lol i did something like what i assume your goal is on my neocities when i detect !!window.chrome === true

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 7 points 2 years ago (6 children)

    Why the double negation?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 12 points 2 years ago (4 children)

    It's a handy way to convert any value to a Boolean. If window.chrome is defined and done non-empty value, double negation turns it into just true.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 6 points 2 years ago (3 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 6 points 2 years ago

    == 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.)

  • permalink
  • fedilink
  • source
  • parent