I · Meaning

Before Beautiful Was an Option

What older systems knew because they had to

Okay. Let's go back in time, to the eighties and early nineties, when DOS ran the computers that did the real work. Those screens lasted far longer than their era. Walk up to the counter at a library, a clinic, a print shop, years after everyone had Windows at home, and plenty of them still ran screens like this one.

A DOS screen was eighty columns and twenty-five rows of characters. Each cell held one character, one color for the character and one for the cell behind it, out of sixteen. That was all of it. No fonts to choose, no rounded corners, no shadows, no images, no animation. If you wanted a line, you drew it out of characters, and it cost you a whole row of a twenty-five-row screen.

A Microsoft Access form wasn't much freer. A grid you placed controls on, a handful of control types, the system's font, a background color. The printed page had paper's limits: a fixed size, two sides, nothing that moves.

People built entire businesses on screens like these. Stock, payroll, patients, orders. And the screens worked.

What did the limits leave?

When there's nothing to decorate with, the work that's left is the work that matters. Where things go. What comes first. What belongs with what. What state each thing is in. Where the person is right now, and where they can go from here.

Nobody on a DOS screen thought much about beautiful, because beautiful wasn't an option. Hierarchy had to be carried by position and brightness, because there was nothing else to carry it. A box drawn in line characters ate a row and a column of a tiny screen, so it got drawn around things that earned it: a window, a dialog, a field you were typing into. Contrast was high because sixteen colors leave no room for the soft grays that make text hard to read. And there was always one cursor. You always knew where you were.

None of that was chosen as a value. It was what was left. The fundamentals were the only thing that mattered, because they were the only things that existed.

What can they still teach?

Not that old was better. Old asked a lot of the person: keys to memorize, messages written for the programmer, no undo, no mercy for the wrong key at the wrong moment. Plenty of what we have now is a real improvement, and nobody should be sentimental about a screen that made you type a command to save.

But look at one of those screens now and you see the fundamentals with nothing covering them. The grid, the order, the hierarchy, the grouping, the contrast, the focus, the state. It's close to an X-ray of a design. And when a modern screen doesn't work, the failure is often one of those same things, hidden under something nicer. The flat dashboard where everything is the same weight. The page in a box in a box. The cursor that's nowhere, so the person has to look for where they are.

<figure data-here="1" style="margin:1.6rem 0;text-align:center"><img src="/figures/caret-catalog.jpg" alt="a library catalog in white and yellow type on deep blue: shelves in a narrow pane on the left, all titles in a wide pane on the right, one row lit as the cursor, and a two-letter shortcut beside every row" style="width:100%;height:auto;display:block;border-radius:2px"><figcaption style="font-size:.8rem;color:#a8a298;font-style:italic;margin-top:.4rem">Not an old screen. A design system I made in 2026 on the old physics: two panes, one cursor that is always somewhere, and, while a key is held, a short code to reach every row.</figcaption></figure>

The freedom we have now is real, and it's also a way to skip the questions. You can make a screen look finished before anyone has decided what comes first on it. The older systems couldn't do that. They couldn't look finished at all. All they could be was clear or unclear.

The limits are gone. The fundamentals aren't. They're just easier to cover up now. Before deciding what something looks like, it's worth asking what it would have been when looking like anything wasn't an option.