the brahmin class
Entry eight of ten in “the end of the wire,” a series on the terminal. Each one stands alone.
Every democratization of computing produced a new priesthood one layer up. The current one is the first that doesn’t look like one.
A Brahmin is not defined by money. The caste is defined by access to sacred text and the authority to perform the ritual correctly — you are what you are permitted to read and permitted to recite, and the boundary is maintained by the fact that most people cannot check your work.
Hold that and let it sit, because the history does the rest.
In the early 1960s you did not use a computer. You wrote your program by hand, someone punched it onto cards, and you carried the deck to a counter and handed it across. The machine was in another room and you were not going in there. Sometime later — that night, the next morning — you got a printout back, and if you had a typo you found out about it then, and you started over.
Corbató and his coauthors put a number on it in 1962, in the paper announcing the system that ended it: “Using current batch monitor techniques, as is done on most large computers, each program bug usually requires several hours to eliminate, if not a complete day.” A missing comma cost you a day. Not because the computer was slow. The computer was fast. The queue was slow, and the queue had a staff.
Everybody reaches for the men in white coats here, and I went looking for them, and what I can actually document is thinner than the image — the coats show up in photographs and in memory, and I’d rather not build an argument on a costume. It doesn’t matter. The load-bearing thing was never the coat. It was the counter. There was a window, and an inside, and an outside, and you knew which side of it you stood on. Nobody had to explain the hierarchy to you. It had a physical address.
Then the terminal arrived, and the terminal was the thing that broke it.
That sentence should land wrong, because the modern reading of a command line is elitism — the interface for people who want you to know they can use it. Historically that is close to backwards. In November 1961, Corbató’s group demonstrated the Compatible Time-Sharing System at MIT: several people at typewriter consoles, at the same time, each one getting the machine’s attention in turn, each one talking to it directly. No counter. No deck. No day.
And the people building it did not describe it as a power tool for experts. They described it as a utility. John McCarthy, in a talk at MIT’s centennial in 1961: “computing may someday be organized as a public utility just as the telephone system is a public utility.” Robert Fano, in his 1964 funding proposal to ARPA, called the thing they had already built a “community utility… capable of supplying computer power to each customer where, when, and in the amount that he needs it.” Corbató’s own 1962 paper reaches for the same image — a computer “made simultaneously available to many users in a manner somewhat like a telephone exchange.”
That is the vocabulary of water and electricity. The interface we now read as a fence was, at the moment of its invention, explicitly the fence being torn down.
So the counter closed. And here is what the counter’s closing did not do.
In 1974 — a dozen years into the timesharing era, a year before the Altair — Ted Nelson published Computer Lib, and the section everyone remembers is titled “The Computer Priesthood.” It opens: “Knowledge is power and so it tends to be hoarded. Experts in any field rarely want people to understand what they do.” The priesthood he names is made of “people who spatter you with unintelligible answers and seem unwilling to give you straight ones,” and he is not writing about the men behind the window. That regime was over. He is writing about the people the terminal had liberated, who had become, in about a decade, the new inside.
Which brings the third act, and this is the one it would be easy to sneer at, so I want to be exact.
The graphical interface was a democratization on a scale the timesharing people never touched. Not hundreds of users. Hundreds of millions. It replaced recall with recognition — the available actions moved out of your memory and onto the screen in front of you — and that single substitution is most of the reason a person with no interest whatsoever in computers owns three of them. Every argument that follows in this post is made possible by a machine descended from that decision, on a screen full of drawn objects, and I am not going to pretend otherwise.
Three democratizations. All three real. And after each one, a smaller room formed one floor up.
The part I have to prove is that the room is real and not a matter of taste, because if the capability difference isn’t there, everything else here is snobbery with footnotes.
So: every file under this directory modified in the last three days, larger than a megabyte, that isn’t tracked in git — move them somewhere else and keep the structure. That’s one sentence. It’s also one line in a shell. Now do it in a file manager. Not slowly — at all. There is no sequence of clicks that expresses it, and the reason isn’t that nobody built the feature.
Pointing can only refer to what is present. That’s the whole limit. You can point at a file because the file is rendered; you cannot point at a category of file, or a file that doesn’t exist yet, or a condition three files might satisfy tomorrow. Linguists have a name for the thing pointing lacks — displacement, in Hockett’s inventory of what makes a language a language: the ability to refer to what is not here. Add productivity, the generation of unlimited expressions from limited parts, and you have exactly the two properties a glob and a pipe supply and a mouse cannot. A wildcard is a quantifier. A pipe is composition. No graphical interface has ever had either, across fifty years of extremely good designers trying.
And the steelman is strong: direct manipulation is a real cognitive victory. Seeing the object you’re acting on eliminates an entire category of error — you cannot typo a file you are dragging, and the confirmation dialog you resent has saved more data than any backup script. That is why it won, and it deserved to.
But you can only manipulate what is drawn. The screen is the boundary of the expressible. The GUI’s greatest strength and its ceiling are the same property, which is not a flaw in any particular GUI and cannot be designed away.
Someone always says: AppleScript, Automator, Shortcuts, node graphs, the formula bar. Yes — and notice what every one of them is. They are languages, bolted onto graphical interfaces, because at some point the pointing ran out. That’s not a rebuttal. That’s the argument, conceded by the vendors, in shipping form.
So the population split. Not into smart and dumb, and not into trained and untrained. Into people for whom a computer is a set of verbs somebody else chose, and people for whom it is a substrate they can address in sentences.
And this hierarchy is worse than the one with the window, for exactly one reason: it is invisible from below.
The batch priesthood was legible. There was a counter, a staff, a wait. You knew you were outside, you knew what outside cost, and you could want to be inside. The current arrangement presents as the absence of hierarchy. Everyone has the same laptop. Nobody is standing between you and the machine. And the ceiling is undetectable from underneath, because you cannot notice the absence of a thing you have no words for. You don’t experience it as I can’t say that. You experience it as an afternoon of clicking, and a vague sense that this should have been easier, and no name for what would have made it easier.
The vocabulary tells on itself, too. A background process is a daemon — and that is not a backronym for Disk And Execution Monitor, which Corbató, who coined the usage at Project MAC around 1963, specifically rejected. He named it after Maxwell’s demon: an imaginary agent that sorts invisibly and works tirelessly and never asks for anything. From there it’s all downhill into liturgy. Wizards. Gurus. Oracles. The kernel. Root. You kill processes and exorcise stale locks and get an incantation wrong. A field that named its own furniture after spirits and priests was not being subtle.
Now the part that costs me something.
Most terminal use is not power. Most of it is habit, identity, and performance. I do not open a shell to do things a graphical tool cannot do; I open a shell because that is where I live and my hands know the way. My dotfiles repository is a coat of arms. It is public. It has a README. Nobody has ever needed my README.
The caste analogy cuts in this direction hardest, and it should. Ritual purity is exactly the right frame for a great deal of this: correct configuration performed correctly, in view of others who can appreciate the correctness. Rebuilding your prompt is not capability. It is vestments. The moment the status economy became visible to me was the moment I noticed I was maintaining it — not that other people were.
Both things are true, and the entry fails if you take only one. The capability difference is real, mechanical, and provable in one sentence about files. The status economy stacked on top of it is mostly theater, and I am in the cast.
The man at the counter took your cards and handed you a day’s wait, and you knew precisely what he had that you didn’t.
There’s no counter now. That was the honest part.