CS Fundamentals
Post #157 · source on Telegram
When int and float clash, SuperNaN swoops in to clarify types
Description
A black-and-white stick-figure comic is split into two panels. In the top panel, a crowd of office-clad figures point upward, shouting through black speech bubbles: "Look! Up in the sky!", "It's an int!", and "It's a float!", separated by a zig-zag lightning divider. The lower panel counters with a large, bold bubble proclaiming "No! It's SuperNaN!" while a caped superhero, emblazoned with "NaN" on the cape, flies left-to-right above a newly cheering crowd. Faces move from puzzled to delighted, emphasizing the twist that the mystery object is the notorious Not-a-Number value. The gag plays on type confusion, floating-point edge cases, and developer frustration, with the small credit "hacktoon.com" in the bottom left
More like this
More like this in CS Fundamentals →
Use J and K for navigation
Comments
7Comment deleted
SuperNaN: the caped value that turns a five-minute code review into a 45-minute debate about IEEE-754, nullability semantics, and who was bold enough to write `if (x == NaN)` in production
After twenty years of explaining to junior devs that NaN !== NaN, I've finally accepted that JavaScript's type system is just performance art disguised as a specification
SuperNaN's only weakness is identity: even he can't equal himself
The real irony? In JavaScript, typeof NaN returns 'number', so both camps are technically wrong - and SuperNaN would fail the identity check since NaN !== NaN. Classic IEEE 754 trolling the entire developer community since 1985
SuperNaN: the only hero whose kryptonite is an equality check - even it ghosts itself with NaN !== NaN
Int or float? In prod it’s SuperNaN - the IEEE 754 antihero that propagates through every aggregation, defeats equals(), and erases your dashboards
SuperNaN: the only hero who isn't equal to himself, yet still propagates through your pipeline, ruins your percentiles, and dodges every equality check