I still don’t understand the
===operatorEdit: I think a more type strict
==? Pretty sure I understand the point of typescript now.> 1 == 1 true > 1 == '1' true > 1 === '1' false(from node REPL)
Basically it’s the real equals sign
The short answer is that your language needs === when it fucked up the semantics of ==, but it’s also too popular and you can’t fix it without breaking half the web.
It’s also important if you’re checking hashes (at least, it was - if you’re using correct hashing algorithm that isn’t ancient, you will not have this problem).
Because if you take for example “0e462097431906509019562988736854” (which is md5(“240610708”), but also applicable to most other hashing algorithms that hash to a hex string), if(“0e462097431906509019562988736854” == 0) is true. So any other data that hashes to any variantion of “0e[1-9]+” will pass the check, for example:
md5("240610708") == md5("hashcatqlffzszeRcrt")that equals to
"0e462097431906509019562988736854" == "0e242700999142460696437005736231"which thanks to scientific notation and no strict type checking can also mean
0462097431906509019562988736854 == 0242700999142460696437005736231
which is
0 == 0`I did use md5 as an example because the strings are pretty short, but it’s applicable to a whole lot of other hashes. And the problem is that if you use one of the strings that hash to a magic hash in a vulnerable site, it will pass the password check for any user who’s password also hashes to a magic hash. There’s not really a high chance of that happening, but there’s still a lot of hashes that do hash to it.
If you’re checking passwords, you should be using constant time string checking, anyway.
More likely, you should let your bcrypt library do it for you.
==but for JavaScript. What you don’t understand is the==of JavaScript.JS’s
==has some gotchas and you almost never want to use it. So===is what==should have been.All examples are true:
"1" == true [1, 2] == "1,2" " " == false null == undefinedIt isn’t that insane. But some invariants that you may expect don’t hold.
"" == 0 "0" == 0 "" != "0"The other comments explains it in pretty good detail, but when I was learning my teacher explained it sort of like a mnemonic.
1 + 1 = 2 is read “one plus one equals two”
1 + 1 == 2 is read “one plus one is equal to two”
1 + 1 === 2 is read “one plus one is really equal to two”
And you hit the nail on the head, is that === is type explicit while == is implicit.
I’d use something like:
= becomes
== equals
=== is identical to
It’s funny how everyone thinks “equals” in this context should be “identical to” when, in normal language, it doesn’t really mean that at all!
Like
==but more strict. The==operator will do type conversion, so0 == ''will actually be true, as an example. Sometimes (honestly, most times) you may want to compare more strictly.See this StackOverflow answer: https://stackoverflow.com/questions/359494/which-equals-operator-vs-should-be-used-in-javascript-comparisons
I wish the assignment operator wasn’t the equal sign.
x 👈 5Ok deal, but that means we need to change the equality operator to 👉👈
You sonnofabitch I’m in!:-P
x 🔫 5the pew pew principle /s
Interpreter: Wait, x is 5?
This code: Always has been.
It is now, if you know what’s good for you.
:=That’s delayed assignment.
procrastination assignment
In Haskell, it’s the same as the mathematical
=symbol.
1+1====2!← dreamberd developer
Basically Java in a nutshell
JS devs should have a font that turns == into ≈.
ChatGpt: 1+1≈2
Reddit: 1+1=your muther (sic, x2)
X: 1+1≈we should violently overthrow the government
4chan: nvm, I don’t want to get banned for saying this one
4chan: “Gamer words”
No, that’s Discord 🙃
cries in PHP
1 + false ? (I have no idea in which order JS would evaluate things as I rarely have to touch that language much anymore)
Don’t forget that
_.isFinite('1')returns true ;)I’m JavaScript developer. I love coding WebApps. JS sucks💩.
Any Verilog devs?
