Identity. “A is literally B” instead of “A equals B”. This is necessary here in JS because if A is the string “-1” and B is the integer -1, JS evaluates A==B as true because reasons
because if A is the string “-1” and B is the integer -1, JS evaluates A==B as true because reasons
Interesting. If it were the other way around, I think I would have been fine with it (i.e. == used for comparison with type like any other language and === without type). But as it stands now I would hate it if I had to write in JS (but I don’t so it’s fine).
It’s not that bad, honestly, just something you get used to. When I switch to C++ after a while, I sometimes write === and when I switch back to JS after some time, I occasionally forget to use ===.
In C++ it’s obviously an error and for JS I have my IDE set to warn me about ==. I think I’ve used == in JS (and PHP) intentionally once in the last ~5 years.
Identity. “A is literally B” instead of “A equals B”. This is necessary here in JS because if A is the string “-1” and B is the integer -1, JS evaluates A==B as true because reasons
Interesting. If it were the other way around, I think I would have been fine with it (i.e.
==used for comparison with type like any other language and===without type). But as it stands now I would hate it if I had to write in JS (but I don’t so it’s fine).It’s not that bad, honestly, just something you get used to. When I switch to C++ after a while, I sometimes write
===and when I switch back to JS after some time, I occasionally forget to use===.In C++ it’s obviously an error and for JS I have my IDE set to warn me about
==. I think I’ve used==in JS (and PHP) intentionally once in the last ~5 years.