dinomug@lemmy.ml to General Programming Discussion@lemmy.ml · 3 years ago7 really good reasons not to use TypeScript | everyday.codeseveryday.codesexternal-linkmessage-square9fedilinkarrow-up115arrow-down12
arrow-up113arrow-down1external-link7 really good reasons not to use TypeScript | everyday.codeseveryday.codesdinomug@lemmy.ml to General Programming Discussion@lemmy.ml · 3 years agomessage-square9fedilink
minus-squareshilangyu (lemmur)@lemmy.mllinkfedilinkarrow-up13·edit-23 years agoI’m so bored of people bringing up NaN !== NaN when talking about “javascript’s wonkiness”. This is defined by IEEE for the floating point standard and it appears any other language using IEEE 754 (which is the majority)
minus-squarehandvat@lemmy.mllinkfedilinkarrow-up5·3 years agoYou shouldn’t attempt comparing 2 floating point numbers with simply == (or === in JavaScript) in most cases and in most languages anyways.
minus-squarespytfyre@lemmy.mllinkfedilinkarrow-up1·3 years agoTotally agree. Moreover I can not think of a valid scenario where you would use such a comparison
I’m so bored of people bringing up NaN !== NaN when talking about “javascript’s wonkiness”. This is defined by IEEE for the floating point standard and it appears any other language using IEEE 754 (which is the majority)
You shouldn’t attempt comparing 2 floating point numbers with simply
==(or===in JavaScript) in most cases and in most languages anyways.Totally agree. Moreover I can not think of a valid scenario where you would use such a comparison