Stop calling it “NaN bread” – NaN is fucking bread!
I want naan bread with my chai tea
I’ll split the check with you! Just gotta run to the ATM machine and I’ll get $20 dollars (as long as I can remember my PIN number)
yup. that’s JavaScript.
there is a game / challenge for this
It is the number that must not be; that cannot be. These 3 letters are all that stand between you and the ultimate cosmic horror.
It is not for nothing that the sender of eight is also known as the soul-render. Which is why a sensible wizard will never mention the number if they can avoid it. “Or you’ll be eight alive.”
The beauty of JavaScript.
You probably haven’t encountered truthsy and falsy values yet?
duh, it’s part of the IEEE 754 standard. every language that handles floating point numbers has NaN handling, and in every language NaN is a float. the only reason this is brought up as a javascript thing all the time is that js doesn’t have separate float and int types (aside from special structures like typed arrays and dataviews), it just defaults to float64 for simplicity and calls it number, which lines up with the “NaN is a number? nani???” joke.
you don’t like it? consult the sorry excuse of thinking sand in the device you’re reading this on, because this is etched straight into it. every FPU capable of handling float32 and float64 numbers knows what NaN is and handles it the exact same way.
this is one of the many things that sound unintuitive about programming but if you bother to understand the context you realise that if it wasn’t this way, it would be way worse. one of the most important skills in our field is to understand computers for what they are, rather than be puzzled that they aren’t what you thought they were, and it especially comes out in edge cases like this.
Excellent, now do nulls!
Counter point: Python.
$ python Python 3.14.4 (main, Aug 20 2026, 10:41:58) [GCC 15.2.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> type(float('nan')) <class 'float'>
To add to this: the state of being not a number is only relevant to a number. Everything that’s already not a number doesn’t need a specific value to represent this state. It’s actually quite logical.
Apparently one of the few examples of JS not being weird.
It is easier to understand the non-weirdness of it in a strongly typed language, IMO. But yes.
Technically everything is a number when you get low enough
Bro I’m too high for this
this makes sense
NaN is a “this was meant to be a number but it somehow isnt”
> “Not a Number”
> Look inside.
> numberI think this, and the fact that NaN == NaN is false, make perfect sense.
NaN is the result of mathematically undefined behavior. You’re not going to get a NaN outside of a number context, so tying it together in the Number scope is fine.Same reason NULL != NULL. It makes sense if you understand how these values work.
That doesn’t smell right.
https://richiban.uk/2016/12/21/does-null-equal-null/
ISNULL may be true, whilst NULL != NULL. NULL is not a value.
Ah, my brain was in C mode, where NULL is functionally 0. This is about the concept, which doesn’t apply equally to all languages.
Yep. There are some languages where this applies, because it’s a mathematical concept. The point is it’s the same ‘no value’ concept, which isn’t
shared byimplemented the same way by all languages.C is strongly typed, and uses pointers, so NULL sort of intrinsically has a value in C.
edit: my wording was a bit off
You can kinda think of it as null meaning undefined. In this case, “undefined does not equal undefined” seems easier for me to wrap my head around
The result of mathematically undefined behaviour should be an error, but sure, go ahead and return Keleven. 1/0 = keleven fuck it.
NaN is one of the ways IEEE maths signals an erroneous calculation when the only outbound communication channel is the returned IEEE value. Reading the history and rationale of the floating-point standard will likely convince you this was and probably is a good compromise.
Because IEEE values often have hardware acceleration that is a significant factor in performance, languages rarely (if ever) choose to map all IEEE error values to language-specific error reporting (e.g. a thrown exception or error-tracking algebraic data type).
JS is hardly an outlier here.
I do think it probably violates the principle of least surprise, but I don’t think I understand the scale of “momentum” change that would need to take place across society (industry, academia, etc.) to align it with naive expectations.
NaN is a error and it’s your responsibility to handle it gracefully. No need to halt the entire program when you fuck up some maths.
NaN is a error
Error.isError(NaN) // Falsenan is a ieee754-defined error. what javascript calls errors these days (it tends to change a lot) has little to nothing to do with that. it’s on every developer to familiarise themself with ieee754, it’s one of the most important documents in the profession.
while nan is an invalid floating-point number, it is a valid value for a float-typed field. making it into an error is like adding a bit labelled “crash” to every number in your program.
please do everyone a favor and stop writing code.
Please do everyone an actual favor and stop doing this. You are harmful and toxic.
No, it should not be an error. If you’re making a calculator and your user enters 1/0, your program should not have the propensity to crash; the result should simply be NaN and you should choose how you display that result to your user.
error ≠ crash
fault v. error v. failure
In common language they can be synonyms, but often aren’t in places (like computing) where there’s a useful difference. A page fault isn’t an error; a handled error doesn’t result in a failure; fault-tolerant systems fail less often than their components fault.
You talk like error handling isn’t a thing.
fun fact: getting NaN from a numeric calculation is the error that you handle. if this wasn’t obvious, please don’t write code for anyone but yourself. hope this helps.
if this wasn’t obvious,
If this wasn’t obvious, be glad of the chance to learn.
If we all stopped as soon as something simple wasn’t obvious, nobody would learn and nobody would do anything.
What a terrible reply to someone. It cuts off curiosity and says “You are too stupid to do anything.”
Yet I bet there was a time that even with that very specific thing, you didn’t think of it that way.
newcomers to shitting on javascript sometimes learn to blame the tool
NaNis a primitive value, not anError.>> typeof 1 / "a" "number"
It feels silly that a high level language has NaN at all
deleted by creator
https://www.destroyallsoftware.com/talks/wat is much better. This post is pretty low-effort.
I love that talk.
And yes, this post is low-effort, but so are most posts on here. Just a bunch of screenshots from various microblogging platforms reposted from Reddit.
Came in here to make sure this is posted.
JavaScript really isn’t as bad as people want it to be
Unfortunately. That’s why it is still so prevalent
That it’s so prevalent could also mean it’s worse than many people realize.
It’s of type Numbn’t.
It’s clearly bread.
Infinityis also a number in JavaScript / IEEE number formats, but you’ll get a lot of grumbling from mathematicians with that sort of assertion.Once you accept that each float represent a range of reals most design decisions make sense.
Infinity is just the name given to values that are too large to represent otherwise and negative zero includes negative values too close to zero.What mathematics probably hate most about floats is that rounding breaks commutativity.
What mathematics probably hate most about floats is that rounding breaks commutativity.
Actually, the maths people in my circles tend to complain more about how the normal floating-point equality test doesn’t define an equivalence relation, but really any of the violations of field properties can attract complaints.
NaN indeed!
