Programmer Humor

32443 readers

973 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.

founded 5 years ago

MODERATORS

[email protected]

Yup, Javascript can go F@#! itself (lemmy.ml)

submitted 1 year ago by [email protected] to c/[email protected]

17 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 1 year ago (2 children)

I'm not sure if you really want to know, but:

greater than, smaller than, will cast the type so it will be 0>0 which is false, ofcourse. 0>=0 is true.

Now == will first compare types, they are different types so it's false.

Also I'm a JavaScript Dev and if I ever see someone I work with use these kind of hacks I'm never working together with them again unless they apologize a lot and wash their dirty typing hands with.. acid? :-)

[–] [email protected] 2 points 1 year ago

isn't === the one that compare types first?

I just tried on node and 0 == '0' returns true

found the real reason

[–] [email protected] 1 points 1 year ago

Not a JavaScript dev here, but I work with it. Doesn't "==" do type coercion, though? Isn't that why "===" exists?

As far as I know the operators ">=" and "<=" are implemented as the negation of "<" and ">" respectively. Why: because when you are working with sticky ordered sets, like natural numbers, those operators work.

Thus "0<=0" -> "!(0>0)" -> "!(false)" -> "true"

Correct me if my thinking is wrong though.