The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Anything that is unrelated to elephants is irrelephant Anonymous - The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944 - Never argue with a fool. Onlookers may not be able to tell the difference. Mark Twain
My old computer has a 64 x 32 or 64 x 64 pixel resolution and a 3x 4 pixel font (all upper case) was used for such things as Tiny BASIC. Memory was a big issue and the font and the routines to draw strings into display memory bloated up the interpreter from 2k to 3k, leaving you with only 1k left for your BASIC programs.
My version of this encodes the full set 0f 96 printable ASCII characters in just 288 bytes and about 256 bytes for the drawing routines, a little over 1/2 k total. My font is not monospaced, so I usually get more than 16 characters per line. As a bonus, the routine that draws the characters can also be used to draw sprites.
Readability is quite a problem with this sort of fonts. You don't have a pixel to spare, but some characters (like Q, M, W, # or &) need a width of 4 or 5. I find it readable and useful enough for a computer from 1976: COSMAC Elf screenshot[^]
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
Thanks for the screenshot! It did some good to grow up on systems like this. CPUs are now so fast, and memory so cheap, that you get folks developing systems that need to scale using approaches like Thread Per User, Thread Per Request, or even Thread Per Object. And then wondering why the system tips over.