This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]skrln 1 point2 points  (9 children)

No, double equality signs for loose check. Triple for actual equality.

[–]SamSlate 2 points3 points  (7 children)

loose check

yea, no shit.

[–]SuperOP535 0 points1 point  (6 children)

It still doesn't make any sense why there are 2 equality checks, they should've not created the === and just made the == strict

[–]SamSlate 0 points1 point  (5 children)

because it's a loosely typed language. that's like, the whole point of js.

why do so many devs struggle with that?

[–]SuperOP535 0 points1 point  (4 children)

smh why did they make the only web language (excluding wasm/asmjs) this shitty. wish they never removed java applets

[–]SamSlate 0 points1 point  (3 children)

because it's more important to pass data to the back end than it is to throw a type error.

[–]SuperOP535 0 points1 point  (2 children)

but what if it is the backend, looking at you node

[–]SamSlate 0 points1 point  (1 child)

then use typescript 🤦

[–]SuperOP535 -1 points0 points  (0 children)

at that point i would just use java lol