Free as in Freedom by Sam Williams (classic books for 13 year olds .TXT) 📖

going toward programming, but I still thought, well, maybe I can do both,” Stallman says.

 

Toiling in the fields of graduate-level science by day and programming in the monastic confines of the AI Lab by night, Stallman tried to achieve a perfect balance.

The fulcrum of this geek teeter-totter was his weekly outing with the folk-dance troupe, his one social outlet that guaranteed at least a modicum of interaction with the opposite sex. Near the end of that first year at MIT, however, disaster struck. A knee injury forced Stallman to drop out of the troupe. At first, Stallman viewed the injury as a temporary problem, devoting the spare time he would have spent dancing to working at the AI Lab even more. By the end of the summer, when the knee still ached and classes reconvened, Stallman began to worry. “My knee wasn’t getting any better,” Stallman recalls, “which meant I had to stop dancing completely. I was heartbroken.”

 

With no dorm and no dancing, Stallman’s social universe imploded. Like an astronaut experiencing the aftereffects of zero-gravity, Stallman found that his ability to interact with nonhackers, especially female nonhackers, had atrophied significantly. After 16 weeks in the AI Lab, the self confidence he’d been quietly accumulating during his 4 years at Harvard was virtually gone.

 

“I felt basically that I’d lost all my energy,”

Stallman recalls. “I’d lost my energy to do anything but what was most immediately tempting. The energy to do something else was gone. I was in total despair.”

 

Stallman retreated from the world even further, focusing entirely on his work at the AI Lab. By October, 1975, he dropped out of MIT, never to go back.

Software hacking, once a hobby, had become his calling.

 

Looking back on that period, Stallman sees the transition from full-time student to full-time hacker as inevitable. Sooner or later, he believes, the siren’s call of computer hacking would have overpowered his interest in other professional pursuits. “With physics and math, I could never figure out a way to contribute,” says Stallman, recalling his struggles prior to the knee injury. “I would have been proud to advance either one of those fields, but I could never see a way to do that. I didn’t know where to start.

With software, I saw right away how to write things that would run and be useful. The pleasure of that knowledge led me to want to do it more.”

 

Stallman wasn’t the first to equate hacking with pleasure. Many of the hackers who staffed the AI Lab boasted similar, incomplete academic r�sum�s. Most had come in pursuing degrees in math or electrical engineering only to surrender their academic careers and professional ambitions to the sheer exhilaration that came with solving problems never before addressed.

Like St. Thomas Aquinas, the scholastic known for working so long on his theological summae that he sometimes achieved spiritual visions, hackers reached transcendent internal states through sheer mental focus and physical exhaustion. Although Stallman shunned drugs, like most hackers, he enjoyed the “high” that came near the end of a 20-hour coding bender.

 

Perhaps the most enjoyable emotion, however, was the sense of personal fulfillment. When it came to hacking, Stallman was a natural. A childhood’s worth of late-night study sessions gave him the ability to work long hours with little sleep. As a social outcast since age 10, he had little difficulty working alone. And as a mathematician with built-in gift for logic and foresight, Stallman possessed the ability to circumvent design barriers that left most hackers spinning their wheels.

 

“He was special,” recalls Gerald Sussman, an MIT

faculty member and former AI Lab researcher. Describing Stallman as a “clear thinker and a clear designer,”

Sussman employed Stallman as a research-project assistant beginning in 1975. The project was complex, involving the creation of an AI program that could analyze circuit diagrams. Not only did it involve an expert’s command of Lisp, a programming language built specifically for AI applications, but it also required an understanding of how a human might approach the same task.

 

When he wasn’t working on official projects such as Sussman’s automated circuit-analysis program, Stallman devoted his time to pet projects. It was in a hacker’s best interest to improve the lab’s software infrastructure, and one of Stallman’s biggest pet projects during this period was the lab’s editor program TECO.

 

The story of Stallman’s work on TECO during the 1970s is inextricably linked with Stallman’s later leadership of the free software movement. It is also a significant stage in the history of computer evolution, so much so that a brief recapitulation of that evolution is necessary. During the 1950s and 1960s, when computers were first appearing at universities, computer programming was an incredibly abstract pursuit. To communicate with the machine, programmers created a series of punch cards, with each card representing an individual software command. Programmers would then hand the cards over to a central system administrator who would then insert them, one by one, into the machine, waiting for the machine to spit out a new set of punch cards, which the programmer would then decipher as output. This process, known as ” batch processing,” was cumbersome and time consuming. It was also prone to abuses of authority. One of the motivating factors behind hackers’ inbred aversion to centralization was the power held by early system operators in dictating which jobs held top priority.

 

In 1962, computer scientists and hackers involved in MIT’s Project MAC, an early forerunner of the AI Lab, took steps to alleviate this frustration. Timesharing, originally known as “time stealing,” made it possible for multiple programs to take advantage of a machine’s operational capabilities. Teletype interfaces also made it possible to communicate with a machine not through a series of punched holes but through actual text. A programmer typed in commands and read the line-by-line output generated by the machine.

 

During the late 1960s, interface design made additional leaps. In a famous 1968 lecture, Doug Engelbart, a scientist then working at the Stanford Research Institute, unveiled a prototype of the modern graphical interface. Rigging up a television set to the computer and adding a pointer device which Engelbart dubbed a “

mouse,” the scientist created a system even more interactive than the time-sharing system developed a MIT. Treating the video display like a high-speed printer, Engelbart’s system gave a user the ability to move the cursor around the screen and see the cursor position updated by the computer in real time. The user suddenly had the ability to position text anywhere on the screen.

 

Such innovations would take another two decades to make their way into the commercial marketplace. Still, by the 1970s, video screens had started to replace teletypes as display terminals, creating the potential for full-screen-as opposed to line-by-line-editing capabilities.

 

One of the first programs to take advantage of this full-screen capability was the MIT AI Lab’s TECO. Short for Text Editor and COrrector, the program had been upgraded by hackers from an old teletype line editor for the lab’s PDP-6 machine.ccording to the Jargon File, TECO’s name originally stood for Tape Editor and Corrector.

 

TECO was a substantial improvement over old editors, but it still had its drawbacks. To create and edit a document, a programmer had to enter a series of software commands specifying each edit. It was an abstract process. Unlike modern word processors, which update text with each keystroke, TECO demanded that the user enter an extended series of editing instructions followed by an “end of command” sequence just to change the text.Over time, a hacker grew proficient enough to write entire documents in edit mode, but as Stallman himself would later point out, the process required “a mental skill like that of blindfold chess.“See Richard Stallman, “EMACS: The Extensible,

Customizable, Display Editor,” AI Lab Memo (1979). An updated HTML version of this memo, from which I am quoting, is available at

http://www.gnu.org/software/emacs/emacs-paper.html.

 

To facilitate the process, AI Lab hackers had built a system that displayed both the “source” and “display”

modes on a split screen. Despite this innovative hack, switching from mode to mode was still a nuisance.

 

TECO wasn’t the only full-screen editor floating around the computer world at this time. During a visit to the Stanford Artificial Intelligence Lab in 1976, Stallman encountered an edit program named E. The program contained an internal feature, which allowed a user to update display text after each command keystroke. In the language of 1970s programming, E was one of the first rudimentary WYSIWYG editors. Short for “what you see is what you get,” WYSIWYG meant that a user could manipulate the file by moving through the displayed text, as opposed to working through a back-end editor program.“See Richard Stallman, “Emacs the Full Screen Editor”

(1987).

http://www.lysator.liu.se/history/garb/txt/87-1-emacs.txt Impressed by the hack, Stallman looked for ways to expand TECO’s functionality in similar fashion upon his return to MIT. He found a TECO feature called Control-R, written by Carl Mikkelson and named after the two-key combination that triggered it. Mikkelson’s hack switched TECO from its usual abstract command-execution mode to a more intuitive keystroke-by-keystroke mode. Stallman revised the feature in a subtle but significant way. He made it possible to trigger other TECO command strings, or “

macros,” using other, two-key combinations. Where users had once entered command strings and discarded them after entering then, Stallman’s hack made it possible to save macro tricks on file and call them up at will.

Mikkelson’s hack had raised TECO to the level of a WYSIWYG editor. Stallman’s hack had raised it to the level of a user-programmable WYSIWYG editor. “That was the real breakthrough,” says Guy Steele, a fellow AI Lab hacker at the time.

 

By Stallman’s own recollection, the macro hack touched off an explosion of further innovation. “Everybody and his brother was writing his own collection of redefined screen-editor commands, a command for everything he typically liked to do,” Stallman would later recall.

“People would pass them around and improve them, making them more powerful and more general. The collections of redefinitions gradually became system programs in their own right.”

 

So many people found the macro innovations useful and had incorporated it into their own TECO programs that the TECO editor had become secondary to the macro mania it inspired. “We started to categorize it mentally as a programming language rather than as an editor,”

Stallman says. Users were experiencing their own pleasure tweaking the software and trading new ideas.

 

Two years after the explosion, the rate of innovation began to exhibit dangerous side effects. The explosive growth had provided an exciting validation of the collaborative hacker approach, but it had also led to over-complexity. “We had a Tower of Babel effect,” says Guy Steele.

 

The effect threatened to kill the spirit that had created it, Steele says. Hackers had designed ITS to facilitate programmers’ ability to share knowledge and improve each other’s work. That meant being able to sit down at another programmer’s desk, open up a programmer’s work and make comments and modifications directly within the software. “Sometimes the easiest way to show somebody how to program or debug something was simply to sit down at the terminal and do it for them,” explains Steele.

 

The macro feature, after its second year, began to foil this capability. In their eagerness to embrace the new full-screen capabilities, hackers had customized their versions of TECO to the point where a hacker sitting down at another hacker’s terminal usually had to spend the first hour just figuring out what macro commands did what.

 

Frustrated, Steele took it upon himself to the solve the problem. He gathered together the four different macro packages and began assembling a chart documenting the most useful macro commands. In the course of implementing the design specified by the chart, Steele says he attracted Stallman’s attention.

 

“He started