When the slashed zero fixes and reintroduces zero-vs-O confusion for developers
Description
Screenshot of a Wikipedia-style page section titled “Science, technology and engineering.” Under the heading, two black bullet points are shown in a serif font on a white background. Bullet 1 reads, “Slashed zero (Ø), a representation of the number 0 (zero) to distinguish it from the letter O.” Bullet 2 reads, “Slashed letter 'O' (Ø), a representation of the letter O to distinguish it from the number 0 (zero).” Both bullets hyperlink the phrases “Slashed zero” and “Slashed letter 'O'.” The identical glyph Ø is used for both explanations, creating an ironic loop: the same symbol is recommended to differentiate each character from the other. Developers frequently battle this ambiguity in source code, logs, and terminal output where misreading 0 and O can introduce bugs or mis-typed identifiers, highlighting ongoing issues of font choice, code readability, and ergonomic tooling
Comments
24Comment deleted
Added Ø to stop the O/0 mix-ups; now grep misses half the logs, HMACs don’t match, and Kubernetes is happily running Ø replicas - problem solved
We've successfully solved the O/0 problem by creating two incompatible standards that now require a third disambiguation guide to explain which disambiguation you're using
Ah yes, the classic solution to the zero-vs-O problem: use the exact same glyph (Ø) for both, but with different *intentions*. It's like resolving merge conflicts by committing both versions to the same line and hoping the compiler understands context. This is what happens when your disambiguation strategy needs its own disambiguation strategy - truly a O(Ø) solution to a Ø(O) problem
Fixed 0/O with slashed Ø; then added slashed O as Ø. Now debug which slash means what in prod logs
Typography’s heisenbug: when your editor says Ø is both 0 and O, -O0 quietly ships as -OO and you learn why fonts belong in the postmortem
Ø: the Schrödinger’s glyph - simultaneously zero and O until your ASCII-only parser collapses it into an incident
Why? Just why? Comment deleted
i d0nt kn0w man ¯\_(ツ)_/¯ Comment deleted
to distinguish them from one another, obviously Comment deleted
That's all you need to know about scientific notation reliability Comment deleted
Empty set ∅ moment to distinguish from Ø Comment deleted
Your pfp is deliberately the DisplayPort logo? Comment deleted
Well it lined up with my internet nickname So I thought to drop it on a gradient and call it a day Comment deleted
wtf Comment deleted
That_xkcd_comic_about_standards.jpg Comment deleted
https://m.xkcd.com/927/ Comment deleted
Danish and Norwegians be like... "Am I a spøk to you?" Comment deleted
What page was this from? Comment deleted
Fake Comment deleted
Not really fake, otherwise there would be no need for consensus on what to not use 😄 Comment deleted
https://en.wikipedia.org/wiki/%C3%98_(disambiguation) Comment deleted
Send the link then Comment deleted
Here is the link. https://en.wikipedia.org/wiki/%C3%98_(disambiguation) Comment deleted
Also the obsolete and wrong way: https://en.wikipedia.org/wiki/Slashed_zero#Combining_solidus Comment deleted