nothing on this screen wants anything from me
Entry two of ten in “the end of the wire,” a series on the terminal. Each one stands alone.
Count the things on your screen that are trying to get you to do something.
Not the things you opened. The other ones. The red dot on the app you haven’t launched in a month. The badge with a number in it. The “upgrade” tucked into the corner of a window you use for free. The row of suggestions under the thing you actually wanted. The banner about a feature that shipped in a release you didn’t ask for. The notification that arrived while you were counting.
Every one of those is a small piece of engineering that exists because someone measured what happens when it’s there and what happens when it isn’t, and the version with it won.
Now open a terminal.
A prompt. A cursor. It blinks at a rate somebody picked in the seventies and nobody has revisited since, because there’s no reason to. Nothing is upsold. Nothing is suggested. No element on that screen has a conversion rate attached to it. The terminal is the last computing surface with no attention economy inside it.
The easy explanation is that this is a matter of taste — that terminal people are austere, that the aesthetic is a kind of asceticism, that the purity is chosen. That’s flattering and it’s wrong. The terminal isn’t clean because its users are disciplined. It’s clean because there’s nowhere to put the ad.
Think about what an ad requires. It requires an impression: a moment where the system knows you saw the thing. It requires a surface with stable coordinates, so the thing can be placed. It requires dwell time, so the placement can be priced. It requires a funnel, so the price can be justified.
A shell has none of that. Output scrolls. There is no position on the screen that means anything, because the screen is a river. There is no dwell time, because the thing you’re looking at was printed and then it was gone. There is no impression, because nothing between the program and the terminal is counting. ls prints its output and exits. It does not know whether you read it. Nobody wrote the code path where it would find out.
The medium refuses the business model. Not on principle — structurally. You could put a sponsored line in the middle of df -h output and someone would have a patch reverting it before lunch, but the deeper reason it doesn’t happen is that the sponsored line would be worth almost nothing. Untargeted, unmeasured, in a font the user chose, in a color scheme the user chose, scrolled off the top of the buffer four seconds later. There’s no economics in it.
That’s the same reason a hammer doesn’t have ads on it. Not virtue — geometry. Nobody figured out how to rent it back to you.
The honest part: this is changing at the edges, and it’s changing from the direction you’d expect. Not the terminal — the things you run in it. Package registries know exactly what you installed and when. CLI tools ship with telemetry on by default and an opt-out you have to go find. Some of them print a suggestion after a successful run, and the suggestion is a product. The command line itself has no attention economy in it, but the ecosystem hanging off it is being surveyed, and surveying is always the first step. You don’t monetize a territory you haven’t mapped.
So the claim is narrower than it sounds. The terminal isn’t immune. It’s just uncolonized, and it’s uncolonized for boring economic reasons rather than good ones. The moment someone works out how to price a blinking cursor, the cursor gets a sponsor.
Until then it’s the only screen I look at where the software has no opinion about how long I stay. I type, it runs, it stops. If I walk away mid-command, nothing tries to win me back. There’s no re-engagement path because there’s no engagement to re-establish. It was never trying.
The prompt is still just waiting.