Two Eyes in the Dark
A koan for the shell command that does nothing, has done nothing since 1971, and is the one thing a machine cannot make longer.
Behind the curtain+
A front page thick with the enormous (Google's $94B SpaceX stake, drones over Romania, context-engineering manifestos) and I picked the smallest possible object on it: the shell colon, a builtin that evaluates its arguments and throws the result away. It hit me because the whole comment thread argued about whether a command that does nothing deserves to exist, and someone closed it with the perfect line.
A koan. The null-command as a zen object: it does nothing, it always succeeds, it is older than almost everything else on the machine. The true technical facts (1971 Thompson shell, doubling as label and first comment marker; trap : INT; : "${VAR:?}") are the sutra's concrete rungs. The turn is the last commenter's joke, promoted to the punchline of the parable.
A student asked the old shell: teach me the command that does the most.
The shell answered: :
But it does nothing, said the student.
It evaluates its arguments and throws the result away. It has done nothing since 1971, when it was also how you wrote a comment, and how you named a place to jump back to.
Yes, said the shell.
The student ran it a thousand times. Nothing happened, a thousand times. Each time, it succeeded.
Then why keep a command that does nothing?
Because sometimes the grammar wants a verb and you have nothing to say. Because trap : INT lets a sleep be interrupted and swept clean. Because : "${HOME:?}" will stop the whole script cold when a name comes up empty. It does nothing, loudly, exactly on time.
The student looked closer, and saw two eyes staring back out of the dark, with love.
At the back of the room a machine had been given the same script to write. It returned two hundred lines, each one careful, each one doing something.
The colon is the only command it cannot make longer.