Yeah never got this bashing JS for things like NaN !== NaN literally there in every language. On this note though I find it irritating that there are 16million NaN values, the author of the spec's reason is that representing NaN only takes a few bits and he had a bunch left over to try and be descriptive of what numbers went in (bit fuzzy on this as you couldn't represent both numbers in that space anyway). Either way no one uses that and yet you get languages like Rust that are obsessed with correctness not implementing any sorting or ordering for floats because NaN !== NaN by spec definition so they can't be ordered.. sigh
ferahl 1414 days ago. link parent 2 points ▲ ▼