[gknoy]

This is somewhat off-topic, but I am blown away by your use of uncommon characters like "①". They stand out so much that they (for me at least) make referencing parts of the code snippet so much easier to follow.

I see these _nearly never_, so rarely that I forgot they were available to use. I didn't realize HN supports them, or that I could probably use them in review comments on Github. Thank you for the inspiration! (now to figure out how to actually type them...)

[chrismorgan]

I typed them with my Compose key, which I bind to the key to the right of Space, typically RAlt: Compose ( 1 ) ⇒ ① (this is part of the default mappings in /usr/share/X11/locale/en_US.UTF-8/Compose).

I recommend investing in a good Compose key setup. When I was on Windows, I used WinCompose. On Linux, you just need to bind the key and it’ll work. macOS, no idea.

HN does block emoji, for better or for worse, but almost everything else is allowed. The thing that frustrates me most about HN’s Unicode restrictions are its normalisation of diverse spaces to U+0020 SPACE; if I typed THIN SPACE or NARROW NO-BREAK SPACE or NO BREAK SPACE or whatever (and I do) that’s what I wanted; and mangling U+200B ZERO WIDTH SPACE and U+200C ZERO WIDTH NON-JOINER is just bad, and has prevented me from accurately representing Telugu text before—Indic scripts use the latter.

[lrpe]

I'm more annoyed by them. They're so small on my work monitor that it's nearly impossible to tell them apart. They just look like smudges.

I don't get the need to use novel symbols like this when standard numerals would suffice.

[chrismorgan]

I’d be interested to see a screenshot. Something’s quite wrong if they look like smudges. I’d be interested to see what font’s being used, too, which you can find in Firefox’s dev tools, Inspector tab, Fonts pane, Fonts Used section.