1967
RUNOFF, "Let's stop measuring whitespace with a ruler"
"If I just write .CENTER on one line of the manuscript, the computer can center it for me, right?" That thought from a grad student grumbling through another all-nighter in a basement MIT lab was the beginning of a principle every webpage follows today: keep content and presentation apart.
Writing a research paper as a graduate student in the 1960s was an exhausting ordeal. Want a heading centered on the page? You measured with a ruler and counted exactly how many spaces to type before it. To check that your footnotes had ended up on the bottom of the right page, you traced the lines with your finger. And if you fixed a single sentence, every page after it shifted out of alignment and you had to start over. At MIT, "you'll pull an all-nighter writing one paper" was just folklore.
One graduate student decided to kill the tedium. He had an idea that flipped the problem on its head:
"What I actually want is just 'center this.' So instead of counting spaces myself, why don't I write .CENTER as one line in the manuscript and let the computer figure out the spacing?"
That insight became a program where you sprinkled short directives like .CENTER, .PARAGRAPH, and .FOOTNOTE throughout your text, and the computer read them and laid the page out beautifully on your behalf. The program was called RUNOFF. A colleague at the next desk picked up the first printout and gaped: "You typed a few commands and every footnote landed in the right place by itself!"
It looks small, but this moment is a fork in IT history. "Separate the content from the way it looks" — that simple idea is the same one that will eventually power every webpage in existence. The reason the heading you're reading right now is centered, the reason a news article is laid out cleanly on screen — all of it traces back to a basement lab at MIT in 1967.
RUNOFF mixed simple instructions with the text so the machine handled line breaks and footnotes. It proved that computers could manage document structure, paving the way for later markup languages.