<FourYorkshiremen> Eeee, you were lucky. My first personal computer maxed out at 320x256, or 160x256 if you wanted more than 4 colours. </FourYorkshiremen>
LUXURY. We had 32x24 b&w characters and we were glad of them.
(ZX81, nominally 256x192 pixels but only accessible as 8x8 character cells.)
In the manual, there were some programs you could type in, including "Mars Lander". The calculator shows a landing speed (e.g. "8.2") and then you need to type the thrust adjustment (e.g. -1.0 or +3.0) and then the new landing speed is shown. If you do it right, you land safely and it shows "00000" or something. But nah, that did not happen, you just crash ("11111")
Following that, when I got ZX-81 with 32X24 screen, and like, 1Kb of memory, I was in heaven :)
edit: seems like HN doesn't support these characters but see https://en.wikipedia.org/wiki/Block_Elements
I made a 'zooming through a tunnel' program in assembler once, using them
Although in the context of developing on small screens, they're not very helpful.
(And if you redefined the character set on the fly, you could make things like Forty-Niner. https://www.youtube.com/watch?v=OTTWMIQVznM )
Obviously, nothing. High resolution for most people is still just a 'nice to have.' But even 1080p@15" will produce relatively crisp text. I'd argue East Asian languages are the only ones to significantly improve in legibility, as sub-pixel rendering pretty much does what it needs to do for English nowadays.
That being said, I absolutely will always go for high DPI and everything, I just don't think it's sane to argue it's an absolute must for what amounts to typing and reading text.