• sbv
    link
    fedilink
    English
    arrow-up
    30
    ·
    11 months ago

    Sorry, 0 == '\t'? What?

        • Limitless_screaming@kbin.social
          link
          fedilink
          arrow-up
          22
          ·
          11 months ago

          If " " wasn’t equal to 0, it wouldn’t make sense, but since a string containing a space equals 0, you’d expect the same to apply to a string containing a tab or a newline. (or at least I’d expect that)

          • FaceDeer@kbin.social
            link
            fedilink
            arrow-up
            6
            arrow-down
            1
            ·
            11 months ago

            I admit I have never dabbled in javascript, despite being a proficient programmer. I now dread to ask… would any string that contains only whitespace == 0? " \t\n \t " for example?

            • Limitless_screaming@kbin.social
              link
              fedilink
              arrow-up
              7
              ·
              11 months ago

              Yes, it would. Just like a string of spaces " " == 0, but it isn’t that bad; === is Javascript’s version of == in other languages, and, thus, you should be using it if you don’t want that wonkiness.

              == is just for convenience, like when you want to make sure that the user didn’t leave the form empty and the button shouldn’t be greyed out, and other UI stuff. Without these kinds of features JS wouldn’t be used in so many toolkits.

              • atx_aquarian@lemmy.world
                link
                fedilink
                arrow-up
                2
                ·
                11 months ago

                Ok, I always mistakenly assumed === was the identity operator in JS, too. TIL, thanks! As much as we like to poke fun at JS, every time I’m taught the rationale behind some aspect of it, I find it redeeming and even a little endearing.

                • bitcrafter@programming.dev
                  link
                  fedilink
                  English
                  arrow-up
                  5
                  ·
                  11 months ago

                  The explanation given to you makes it sound like == was deliberately designed to be a more convenient version of ===, but what actually happened was that == used to be the only equality operator in JavaScript, which meant that if you didn’t want it’s auto-coercing behavior then you needed to go out of your way to add additional type checks yourself. Because this was obviously a tremendously inconvenient state of affairs, the === operator was introduced later so that you could test for equality without having to worry about JavaScript doing something clever underneath the hood that you weren’t expecting.

                  • masterspace@lemmy.ca
                    link
                    fedilink
                    English
                    arrow-up
                    2
                    ·
                    edit-2
                    11 months ago

                    The explanation given to you makes it sound like == was deliberately designed to be a more convenient version of ===

                    I mean technically == was deliberately designed to be a more convenient version of other languages’ == operator… Just specifically more convenient for light UI stuff since that was all JavaScript was supposed to be used for at the time (or all they thought it would be used for).

                    But give programmers a way to write and execute a small script and someone will eventually use that to try and write an emulator that emulates the computer it’s running on, so the web evolved into more complicated applications, and then that convenience turned out to be wildly inconvenient, not to mention horribly unexpected for programmers coming from other languages, so then they added the triple equality to match other languages.

      • sbv
        link
        fedilink
        English
        arrow-up
        11
        ·
        11 months ago

        It’s a slash-t in the comment. Maybe kbin has different rendering rules for comments?

    • jtk@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      8
      ·
      11 months ago

      Yeah, it’s true. I knew all the other ones, had to put that one in the dev tools console to believe it. I was just happy to know === continues to be sane in that comparison.

    • Blackmist@feddit.uk
      link
      fedilink
      English
      arrow-up
      5
      ·
      11 months ago

      You have to remember that the underlying principle of JavaScript seemed to be “never throw an error”, even if what it’s being told to do is weapons grade bollocks.