Math.min isn’t the minimum integer; it’s the minimum of a list (and max visa versa)… the min/max of an undefined list is the same… IDK what it is, but this probably the most reasonable of the “WTFs” they could have put there i think… other languages would throw an exception or not compile (which JS definitely SHOULD do instead of this, buuuuut lots of JS has aversions to errors)
*edit: okay the curiosity was killing me: Math.min() is Infinity and Math.max() is -Infinity
I always thought that NaN is required by IEEE rules to never equal any other number, including itself, because you can make NaN in different ways and this shouldn’t result in equality or something, so C is wild but not javascript’s fault.
The other three being true is definitely javascript’s insane fault, though.
It’s C
No, it’s Javascript, keep up
Javascript is basically just C with some syntactical sugar, right? RIGHT?!?
Say when…
To the contrary, it’s Lisp with a lot of syntactic sugar to make it look more like C, but underneath it’s nothing like C. It’s a weird hybrid.
I would say that your username doesn’t check out, but being honest we’re all coders, or at least script kiddie pirates, around here.
For reference.
Wtf? Min > Max???
Math.min isn’t the minimum integer; it’s the minimum of a list (and max visa versa)… the min/max of an undefined list is the same… IDK what it is, but this probably the most reasonable of the “WTFs” they could have put there i think… other languages would throw an exception or not compile (which JS definitely SHOULD do instead of this, buuuuut lots of JS has aversions to errors)
*edit: okay the curiosity was killing me: Math.min() is Infinity and Math.max() is -Infinity
That explains it then. It could be mislead for -inf and +inf
deleted by creator
I always thought that NaN is required by IEEE rules to never equal any other number, including itself, because you can make NaN in different ways and this shouldn’t result in equality or something, so C is wild but not javascript’s fault.
The other three being true is definitely javascript’s insane fault, though.
Completely wrong. I’m hoping this was a joke… :-D