JS shitters will defend this

JS shitters will defend this

Attached: ECg2-YCXUAA85oP.png (562x810, 37K)

Other urls found in this thread:

github.com/denysdovhan/wtfjs/blob/master/README.md
twitter.com/NSFWRedditGif

"b" + "a" + +"a" + "a"; // -> 'baNaNa'

Regardless of how much of a busted language JS is, there's no reason to omit "NaN === NaN" in your image as it would have revealed the underlying principle. Bad thread. Fuck you.

cope

Attached: 2019-08-23-214031_1366x768_scrot.png (1366x768, 17K)

I don't like JS either but this makes sense from a common sense perspective, and an IEEE float perspective.
sdfsdf is not a number
sdfsdf is not the same as everything else that's not a number
isNaN detects any value that isn't a number
"==NaN" isn't something you can/should do in any language using floating point.

seethe

>sdfsdf is not a number
>sdfsdf is not the same as everything else that's not a number
A common sense perspective would lead me to think ===NaN should test whether it is not a number. NaN is a type so equality tests with a type should test whether a value is that type, shouldn't it?

use Number.isNaN()
it doesn't convert

'a' is not a number
'b' is not a number
'a' is not 'b'
This violates what === should do