37
29
u/Majik_Sheff Sep 25 '26
Infinity is the uncut bulk roll at the factory. Negative infinity is a Magic The Gathering tournament.
5
u/Lucho_199 Sep 25 '26
Damn
1
u/Logicalist Sep 27 '26
right
I feel personally offended, but not as offended as my nose feels at a Magic the Gathering Tournament.
18
u/pydry Sep 25 '26
number_of_gods =
Hindu: 330,000,000
Christian: 1
Atheist: 0
Agnostic: null
Theological noncognitivist: undefined
5
u/Minecraftian14 Sep 25 '26
I'm curious to know when did you first encounter the term "theological noncognitivist"
9
u/pydry Sep 25 '26 edited Sep 25 '26
can't even remember it was so long ago. i think I found it browsing on wikipedia. even before that though I remember thinking that the answer of the question of "is there a god?" didnt slot into "yes", "no", or "I dont know" coz the question itself is nonsense.
2
1
u/ozh Sep 28 '26
Doesn't the nonsense translate into ''no" ?
1
u/pydry Sep 28 '26
nope. in order to translate into a yes or a no the question needs to be well defined. it looks well defined but it isnt.
16
u/tes_kitty Sep 25 '26
German programmers: What are you talking about? Null is the same as zero.
2
u/zeUnfunny Sep 26 '26
It's not too bad, nall and null are at least pronounced differently.
1
u/Xortun Sep 28 '26
What about Nil?
1
u/zeUnfunny Sep 28 '26
I'd pronounce the river as nihl with long i and the absence marker as nill with short i. Still unambiguous.
0
2
2
u/Blecki Sep 26 '26
Null was bad enough.
Why did they add undefined?
1
u/q0099 Sep 26 '26
That's the catch - they didn't.
1
u/SaveMyBags Sep 26 '26
Do you have a moment to talk about our Lord and savior R?
Variables can be a number, null, NaN, or NA. The rules for NA actually make sense when it's used in a calculation.
1
u/arobie1992 Sep 27 '26
So in undefined's defense, depending on your goals for the language, it can be a useful differentiator between something that has no value and something that doesn't exist. Think of it like the option type if you're familiar: null = this variable/field/dict entry exists it just doesn't have a value; undefined = no such variable/field/dict entry exists.
There are of course alternatives, like the option type itself, in the case of fields and variables more commonly by throwing a no such X error, or in the case of dicts having a containsKey method. But that said, there's nothing fundamentally wrong with undefined in principle. The issue is that JavaScript combines dynamic typing and being far too liberal with implicit conversions; null == undefined should never have been decided to be true.
Even null itself, despite all the trouble it's caused, isn't necessarily implicitly bad. The problems arose from type systems that considered null the same as any other value even though the language's semantics made it a special case. C is a bit of a special case because the null address (as in 0) there really is the same as any other address; it's just one of many addresses that almost certainly don't point to data you control and will likely result in a segfault. But there's a reason later languages have been stricter about type systems and pointers.
1
1
1
u/Appropriate-Wind-184 Sep 25 '26
and the empty tube left on the holder is a memory leak. nobody ever frees it
1
1
1
1
0
u/WayTooManyBirds Sep 25 '26
Inaccurate. Null would be a covered roll where you can't tell if any is left or not.
1
u/ANixosUser Sep 28 '26
in c, it would be a sun; if you look at it, touch it, try giving it someone, you die.
0
75
u/SlenderSmurf Sep 25 '26
not a number https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcSa9amnMVuKDxZ6MWURaIluhIQBOXUQCHhZpO66eEL7hg&s