> Once the novelty wears off a "practical" example would be rendering "in-game book pages" that don't look like complete gibberish, or an "accurate print preview" with real text instead of blurry placeholder pixels that don't even look close to being the glyphs scaled down.
The lower case letters can mostly be read just in context. Looking at the characters here [0] 'g' is just a vertical solid rectangle and 's' is two diagonal pixels. 'W' looks more like an 'M' than the actual M letter.
[0] https://raw.githubusercontent.com/Michaelangel007/nanofont3x...
I also can't read it at 100% on a high-density monitor, but I can read it very comfortably at a normal size, even though glyphs have so few features.
You wouldn't say that Super Mario is unplayable because it's too tiny at 256x224. You would just have you 4k TV show big pixels and get on with the game.
It's truly impressive feat to get it this small. I used to do texts like this, often manually, pixel by pixel. For websites and games, it was all the rage back in late nineties early 2000s.
But only now I start to truly understand,by experiencing first-hand, why accessibility matters. This font is awesome, but terrible for any kind of accessibility.