• Skyhighatrist@lemmy.ca
    link
    fedilink
    arrow-up
    14
    ·
    1 year ago

    That’s not true these days. You can try it yourself right in your browser’s dev console.

    These results are from Firefox’s console.

    0 == null == undefined
    > false
    0 == null
    > false
    0 == undefined
    > false
    null == undefined
    > true
    null === undefined
    > false
    

    And even in the one case where == says they are the same, you can fix that by making sure you are using === so that it doesn’t do type coercion for the comparison.

            • shrugal@lemm.ee
              link
              fedilink
              arrow-up
              2
              ·
              1 year ago

              What’s confusing about that? It’s null, just two different kinds with slightly different meanings. Is having two boolean values also confusing?! Should we simplify it?

              I mean I can get behind trying to remove null entirely and replacing it with better concepts, but I cannot understand why having one more null value suddenly makes it confusing. You don’t even have to care in 95% of the cases, and it can be useful in the other 5%.

              Honestly, it looks more like some kind of misguided purism to me.