I've never had number naan before... Is it any good? π€
Programmer Humor
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
- If the mod doesn't find it funny, you're banned. Ha-ha!... For real: do not use the community for "statements". There are other places for such content. Keep it chill and funny.
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."
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!
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.
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'>
The beauty of JavaScript.
You probably haven't encountered truthsy and falsy values yet?
Technically everything is a number when you get low enough
Bro I'm too high for this
> "Not a Number"
> Look inside.
> number
this makes sense
NaN is a "this was meant to be a number but it somehow isnt"
I 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 by~~ implemented 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
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.
It's of type Numbn't.
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 clearly bread.
Infinity is 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.
When writing my comment I had successfully repressed that fact in my mind. That's obviously worse.
NaN indeed!
The way I think about it: number is a js type. A floating point double, in other languages.
NaN is a state that a number type can be in, representing a situation where the outcome of the numeric operation cannot be determined.
Anywho, also yea β¦.JavaScript is goofy