In the Beginning...Was the Command Line
4/5
()
About this ebook
This is "the Word" -- one man's word, certainly -- about the art (and artifice) of the state of our computer-centric existence. And considering that the "one man" is Neal Stephenson, "the hacker Hemingway" (Newsweek) -- acclaimed novelist, pragmatist, seer, nerd-friendly philosopher, and nationally bestselling author of groundbreaking literary works (Snow Crash, Cryptonomicon, etc., etc.) -- the word is well worth hearing. Mostly well-reasoned examination and partial rant, Stephenson's In the Beginning... was the Command Line is a thoughtful, irreverent, hilarious treatise on the cyber-culture past and present; on operating system tyrannies and downloaded popular revolutions; on the Internet, Disney World, Big Bangs, not to mention the meaning of life itself.
Neal Stephenson
Neal Stephenson is the #1 New York Times bestselling author of the novels Termination Shock, Fall; or, Dodge in Hell, The Rise and Fall of D.O.D.O. (with Nicole Galland), Seveneves, Reamde, Anathem, The System of the World, The Confusion, Quicksilver, Cryptonomicon, The Diamond Age, Snow Crash, Zodiac, and the groundbreaking nonfiction work In the Beginning . . .Was the Command Line. He lives in Seattle, Washington.
Read more from Neal Stephenson
Snow Crash: A Novel Rating: 4 out of 5 stars4/5Cryptonomicon Rating: 4 out of 5 stars4/5Seveneves: A Novel Rating: 4 out of 5 stars4/5Reamde: A Novel Rating: 4 out of 5 stars4/5Termination Shock: A Novel Rating: 4 out of 5 stars4/5The Rise and Fall of D.O.D.O.: A Novel Rating: 4 out of 5 stars4/5The Diamond Age: Or, a Young Lady's Illustrated Primer Rating: 0 out of 5 stars0 ratingsThe Cobweb: A Novel Rating: 4 out of 5 stars4/5Zodiac Rating: 4 out of 5 stars4/5Hieroglyph: Stories & Visions for a Better Future Rating: 3 out of 5 stars3/5Interface: A Novel Rating: 0 out of 5 stars0 ratingsThe Big Book of Cyberpunk Rating: 4 out of 5 stars4/5Robot Artists & Black Swans: The Italian Fantascienza Stories Rating: 0 out of 5 stars0 ratings
Related to In the Beginning...Was the Command Line
Related ebooks
True Names and the Opening of the Cyberspace Frontier Rating: 4 out of 5 stars4/5The Internet Con: How to Seize the Means of Computation Rating: 5 out of 5 stars5/5Termination Shock: A Novel Rating: 4 out of 5 stars4/5Rainbows End: A Novel with One Foot in the Future Rating: 4 out of 5 stars4/5Overclocked: More Stories of the Future Present Rating: 4 out of 5 stars4/5Robot Artists & Black Swans: The Italian Fantascienza Stories Rating: 0 out of 5 stars0 ratingsContext Rating: 4 out of 5 stars4/5Attack Surface Rating: 4 out of 5 stars4/5Burning Chrome Rating: 4 out of 5 stars4/5Little Brother Rating: 4 out of 5 stars4/5The Artificial Kid Rating: 4 out of 5 stars4/5A Deepness in the Sky Rating: 4 out of 5 stars4/5Marooned in Realtime Rating: 4 out of 5 stars4/5Cyberpunk Rating: 4 out of 5 stars4/5The Rise and Fall of D.O.D.O.: A Novel Rating: 4 out of 5 stars4/5Islands in the Net Rating: 3 out of 5 stars3/5Stand on Zanzibar: The Hugo Award-Winning Novel Rating: 4 out of 5 stars4/5The Cyberiad: Stories Rating: 4 out of 5 stars4/5How to Destroy Surveillance Capitalism Rating: 4 out of 5 stars4/5The Bug: A Novel Rating: 4 out of 5 stars4/5Information Doesn't Want to Be Free: Laws for the Internet Age Rating: 0 out of 5 stars0 ratingsThe Ware Tetralogy Rating: 4 out of 5 stars4/5The Hacker Crackdown: Law and Disorder on the Electronic Frontier Rating: 4 out of 5 stars4/5Void Star: A Novel Rating: 4 out of 5 stars4/5The Children of the Sky Rating: 4 out of 5 stars4/5After the Battle on Starship Hill: Prologue to The Children of the Sky Rating: 3 out of 5 stars3/5Close to the Machine: Technophilia and Its Discontents Rating: 4 out of 5 stars4/5Eclipse Penumbra Rating: 4 out of 5 stars4/5Stations of the Tide Rating: 4 out of 5 stars4/5Schismatrix Plus Rating: 4 out of 5 stars4/5
Reviews for In the Beginning...Was the Command Line
597 ratings15 reviews
- Rating: 5 out of 5 stars5/5A rudimentary knowledge of computers is indispensable nowadays, but it is amazing how little those of us who think we know basic computing actually know about the history of the operating systems that we use every day and how little we think about the impact they have on our views of life. Neal Stephenson has done that thinking for us, however, in a fascinatingly fun read that will make even the most technically averse suddenly feel like they get it. With sophisticated and artistic prose, he manages to find just the right metaphors to explain the differences between operating systems in a way that anyone can understand, managing in the process to speak truth about the human experience. Published in 1999, the book manages to feel more prescient than dated. The author is able to convey the fundamental philosophies behind Apple and Microsoft in ways that explain why little has changed since the days of the iMac and Windows NT, regardless of how many "upgrades" those companies have sold us since. After reading this book, you will look at your operating system of choice, and maybe even yourself, in a new light.
- Rating: 5 out of 5 stars5/5Wonderful novel and a timeless classic.This work has the potential to open the mind of the reader to other ways of approaching life and considering the role of men and women in society.The story is deceptively simple and a familiar format for science fiction but Le Guin creates a world so believable you will be convinced it must exist somewhere in the universe.Themes of love, friendship, compassion and sacrifice are subtly drawn to give the reader an experience at once satisfying and uplifting.James Pope
- Rating: 4 out of 5 stars4/5I enjoyed reading about older technology, and reading the perspective of a pre millenial hacker, it actually inspired me to start using Linux again.
- Rating: 5 out of 5 stars5/5Excellent explanation of the OS/hardware wars between Microsoft and Apple. The nature of the battle has changed since this was written, but its still an excellent distillation of the history of the industry.
- Rating: 4 out of 5 stars4/5It's a fun book. Neal writes from the perspective of someone dropped into the operating systems world right about the time that some things were vanishing, and others were just coming into their own.
For a better, more interesting overview, I recommend Peter H. Salus's "A Quarter Century of UNIX" or Katie Hafner and Matthew Lyon's "Where Wizards Stay Up Late: The Origins of the Internet." Actually, you should read them both.
As a sad note, this book was not printed on acid free paper, and I can see that it's already beginning to yellow, just a tiny bit. - Rating: 3 out of 5 stars3/5This is an odd little essay about the nature of computer systems and user interfaces, though it's a little too dated to truly inform today's users except in a very broad sense.
For example, Stephenson proclaims his love for Linux, but reassures us it's actually pretty hard to use -- which is no longer true (most Linux distros offer nice, clean, *fast* GUIs that I prefer to Windows and the Mac).
He deconstructs the earlier years of Apple and Microsoft in an amusing and interesting way, and while his analogies often run pretty far afield, they do serve to illustrate the essential madness that defined Apple and Microsoft in the 1990s.
The value in this (for me) was his explanation of open source development and what it offers the end user. I arrived at many of the same conclusions independently (I was a hardcore Mac user from 1985 to 1995 when the Mac's constant crashes pushed me to Windows, though after a few days with Windows Vista on a new laptop, I installed Ubuntu Linux, which is now an easy-installing, easy-to-use OS).
I now run my 25 year-old marketing and consulting business from four Linux machines, so I understand Stephenson's love of the OS.
I'm less understanding of some of the wild digressions found in the book, and ultimately think I'm giving it three stars instead of two because I think several of his points are spot on (if a little hard to uncover).
For example, Writers should probably heed his warnings about proprietary file formats -- as a fulltime professional writer, 95% of my copy is written on programmer's text editors (including the Emacs editor Stephenson mentions in the book).
And yes, Linux is hugely elegant and offers users a choice of GUI or command line (it's not a coincidence the Mac OS is built atop a free version of Unix).
Interestingly, Stephenson -- a longtime Emacs text editor proponent -- said in an interview his latest book (Reamde) was written in Scrivener, a commercial Mac-only piece of writer's software that makes it easy to stitch together (and rearrange) scenes and chapters of a book.
I don't know if that means he's abandoned his beloved Linux in favor of the Mac (there is now a beta version of Scrivener available for Mac & Linux, though I don't believe it was available when he wrote the book), but it does mean portions of this book are no longer accurate. - Rating: 4 out of 5 stars4/5At 160 pages, this slim volume is more of an extended essay than a full-blown book. Even at that brief length, however, what Stephenson attempts is fairly audacious: a history of personal-computer operating systems from 1984 to 1999; an introduction to Linux and the concept of free, open-source software; and (for lack of a better term) a philosophical inquiry into the nature of operating systems and their impact on the way users interact with and think about computers. That's a tall order for 160 pages, and it's not all equally successful.
The historical survey of the contrasting approaches to operating-system development taken by Microsoft and Apple is fascinating, but it is brief: a history of concepts and business models rather than of the evolution of either Windows or Mac OS as actual pieces of usable software. The introduction to Linux is equally brief, but (from my non-Linux-using perspective) more comprehensive and more successful at conveying a sense of what Linux is and how it works. Stephenson's heart, however, is clearly in the third section of the book: The philosophical discussion of operating systems. He writes with eloquence and considerable passion about the power, flexibility, and customizability of Unix and Linux (its free, open-source descendent), and bemoans the preference of 98% of computer users for the expensive, bug-ridden, failure-prone, heavily mediated commercial alternatives: Windows and Mac OS.
A lot of this philosophical material is interesting, regardless of what operating system one uses. Stevenson makes interesting points about graphical user interfaces (GUIs) and "mediated experience," about the differences between Windows and Linux tech support, and a dozen other things as well. He is frequently insightful, nearly always amusing to read, and makes an honest attempt to understand the position of the 98% of computer users who don’t think like he does. Yet, at some fundamental level, he Doesn't Get It.
The most fundamental division in the computer-using world may be that separating those who care about how their OS works and those who care that it works. Stephenson clearly belongs to the first group and is just as clearly writing for members of the second group (his own cohort already knows the difference between source code and object code, the meaning of "open source," and other things he explains with such admirable clarity). Stephenson frames his arguments, however, as if he was writing for his own group . . . not those of us on the other side of the divide. He lauds the power, flexibility, and adaptability of Linux with the verve of someone who sees them as absolute virtues. He describes the steep learning curve and in-your-face complexity of Linux with the diffidence of someone who sees them as a challenge. Most of his intended audience would likely differ with him on both counts. The moderately powerful, flexible, reliable "devil you know" is, for most users, likely preferable to the more powerful, flexible, and reliable – but utterly alien – system that it would take months or years to become comfortable with, if that devil does the tasks they require of it with reasonable speed and efficiency. Usability is not a cardinal virtue on Stephenson's side of the divide, but it is perhaps the cardinal virtue on the side occupied by most rank-and-file users.
None of this renders Stephenson's arguments void . . . Linux does have huge advantages, and the future of operating systems may well lie in free, open-source software. It does, however, give both author and book a huge blind spot, symbolized by Stephenson's apparent puzzlement that Linux hasn't triumphed yet. - Rating: 5 out of 5 stars5/5Anyone who wants to understand operating systems needs to read this. It's a little dated, as Apple has moved to OSX since it was written, but it gives an insight to operating system mentalities that I have never seen anywhere else.
- Rating: 5 out of 5 stars5/5This essay will forever remind me of hacking in the 90s. It captured the zeitgeist perfectly, with wit and clarity.
- Rating: 3 out of 5 stars3/5Stephenson goes on a rant, amusing for the most part, to make the argument that computer operating systems (OS's) inherently lend themselves to crowd-sourcing, and it is bad business strategy on the part of Microsoft, Apple, and any other business to commit themselves to maintaining a proprietary OS. Overall, his argument is persuasive.
Along the way, he discusses the concept and consequences of the metaphors employed in various OS's, especially those linked to GUIs; argues the strengths & weaknesses of Microsoft (a software company) and Apple (a hardware company); and explores the merits of a few other OS's (notably, UNIX, LINUS, and BeOS -- the latter of which I'd never heard of).
Very nice primer on a variety of topics, though naturally the historical overview ends in 1999 when it was written. - Rating: 4 out of 5 stars4/5The book is a good read and offers interesting insights into the command line versus GUI discussion. But it was published in 1999, before the internet got really big, before Google got really big. Microsoft still is around, so is Apple. BeOs however didn't survive, unlike Linux.
Still, many of the lessons the book tries to bring across and many of the metaphors still apply. - Rating: 4 out of 5 stars4/5A pretty basic review... I like Stephenson's writing, but the topic that he covers uses dated information.
(Talking about the computer industry in 2000? Gasp!)
I liked the 'Unix Philosophy' better. - Rating: 5 out of 5 stars5/5i love this. This work not only highlights the power of a great operating system, it shows us how our laziness and convenience-laden society has left us vulnerable and weak. not strictly about computers at all, but about us as users.
- Rating: 2 out of 5 stars2/5Witty in the usual Stephenson way, and with some interesting observations about popular culture. But at the end of the day, I think Stephenson doesn't really understand computers and so makes the same silly mistakes as so many other people, like assuming that UNIX the OS equals UNIX the user environment.
My understanding is that he's now a little ashamed of this book and realizes just how wrong he was in many parts of his rant. - Rating: 4 out of 5 stars4/5Quick and Fun: "In the Beginning... was the Command Line" is that rarest of specimens: a short book written by Neal Stephenson. In truth, "Command Line" isn't really a book. It began its life as an online post, and was only published after the fact. In it, Stephenson sketches out a brief outline of the development of computers - especially personal computers and their operating systems - during the 1980s and '90s. It is a quick and fun read, filled with Stephensonian humor and creative metaphors that both entertain and enlighten.
In the course of "Command Line," Stephenson briefly touches on the basics of programming before moving on to discuss the history of operating systems over the last twenty years. He looks at the main operating systems out there (specifically Mac, Windows, Linux, BeOS), how they evolved, and their attractions and advantages. His main points are that "it is the fate of operating systems to become free" and that Microsoft's commitment to maintaining its own closed operating system will cripple its broader software development activities, much in the way Apple was hurt by its insistence on producing its own hardware. Though not much is developed, there is a lot of interesting food for thought in these few pages.
Stephen works largely through metaphors, and "Command Line" is written for the layperson. Few people should have any difficulty getting through the book, even without computer experience. Amazon's insistence that the book was written "for an audience of coders and hackers" strikes me as bizarre. There is almost nothing technical in "Command Line," and what is technical (a brief discussion of the Linux file tree is the only topic that comes to mind) is not critical to understanding any of his points and arguments.
In addition to summarizing the history of operating systems, Stephenson also considers some related cultural topics, such as the significance of the graphical user interface as opposed to the command line. Although some of this was interesting, there were a few digressions I thought didn't work particularly well, and which I would have expected to be edited out (or at least significantly revised) before publishing.
Although "Command Line" was written five years ago (a long time in the computer world), its age does not damage it much (especially in the historical sections). If you're interested in the history of personal computing over the last twenty years, "In the Beginning... was the Command Line" is a quick read that can serve as an entertaining introduction. Although it doesn't have much substance, it still manages to make many interesting points. Unless you are a hard-core Stephenson fanatic, "Command Line" is probably not worth purchasing. Since it was originally nothing more than a post on the Internet, it can still easily be found online.
Book preview
In the Beginning...Was the Command Line - Neal Stephenson
About twenty years ago Jobs and Wozniak, the founders of Apple, came up with the very strange idea of selling information-processing machines for use in the home. The business took off, and its founders made a lot of money and received the credit they deserved for being daring visionaries. But around the same time, Bill Gates and Paul Allen came up with an idea even stranger and more fantastical: selling computer operating systems. This was much weirder than the idea of Jobs and Wozniak. A computer at least had some sort of physical reality to it. It came in a box, you could open it up and plug it in and watch lights blink. An operating system had no tangible incarnation at all. It arrived on a disk, of course, but the disk was, in effect, nothing more than the box that the Operating System (OS) came in. The product itself was a very long string of ones and zeroes that, when properly installed and coddled, gave you the ability to manipulate other very long strings of ones and zeroes. Even those few who actually understood what a computer operating system was were apt to think of it as a fantastically arcane engineering prodigy, like a breeder reactor or a U-2 spy plane, and not something that could ever be (in the parlance of high tech) productized.
Yet now the company that Gates and Allen founded is selling operating systems like Gillette sells razor blades. New releases of operating systems are launched as if they were Hollywood blockbusters, with celebrity endorsements, talk show appearances, and world tours. The market for them is vast enough that people worry about whether it has been monopolized by one company. Even the least technically minded people in our society now have at least a hazy idea of what operating systems do; what is more, they have strong opinions about their relative merits. It is commonly understood, even by technically unsophisticated computer users, that if you have a piece of software that works on your Macintosh, and you move it over onto a Windows machine, it will not run. That this would, in fact, be a laughable and idiotic mistake, like nailing horseshoes to the tires of a Buick.
A person who went into a coma before Microsoft was founded, and woke up now, could pick up this morning’s New York Times and understand everything in it—almost:
Item: the richest man in the world made his fortune from—what? Railways? Shipping? Oil? No, operating systems. Item: the Department of Justice has tackled Microsoft’s supposed OS monopoly with legal tools that were invented to restrain the power of nineteenth-century robber barons. Item: a woman friend of mine recently told me that she’d broken off a (hitherto) stimulating exchange of e-mail with a young man. At first he had seemed like such an intelligent and interesting guy, she said, but then, he started going all PC-versus-Mac on me.
What the hell is going on here? And does the operating system business have a future, or only a past? Here is my view, which is entirely subjective; but since I have spent a fair amount of time not only using, but programming, Macintoshes, Windows machines, Linux boxes, and the BeOS, perhaps it is not so ill-informed as to be completely worthless. This is a subjective essay, more review than research paper, and so it might seem unfair or biased compared to the technical reviews you can find in PC magazines. But ever since the Mac came out, our operating systems have been based on metaphors, and anything with metaphors in it is fair game as far as I’m concerned.
Contents
Cover
Title Page
MGBs, Tanks, and Batmobiles
Bit-Flinger
GUIs
Class Struggle on the Desktop
Honey-Pot, Tar-Pit, Whatever
The Technosphere
The Interface Culture
Morlocks and Eloi at the Keyboard
Metaphor Shear
Linux
The Hole Hawg of Operating Systems
The Oral Tradition
OS Shock
Fallibility, Atonement, Redemption, Trust, and Other Arcane Technical Concepts
Memento Mori
Geek Fatigue
Etre
Mindshare
The Right Pinky of God
About the Author
Also by Neal Stephenson
Copyright
About the Publisher
MGBs, Tanks, and Batmobiles
Around the time that Jobs, Wozniak, Gates, and Allen were dreaming up these unlikely schemes, I was a teenager living in Ames, Iowa. One of my friends’ dads had an old MGB sports car rusting away in his garage. Sometimes he would actually manage to get it running, and then he would take us for a spin around the block, with a memorable look of wild youthful exhilaration on his face; to his worried passengers, he was a madman, stalling and backfiring around Ames, Iowa, and eating the dust of rusty Gremlins and Pintos, but in his own mind he was Dustin Hoffman tooling across the Bay Bridge with the wind in his hair.
In retrospect, this was telling me two things about people’s relationship to technology. One was that romance and image go a long way toward shaping their opinions. If you doubt it (and if you have a lot of spare time on your hands), just ask anyone who owns a Macintosh and who, on those grounds, imagines him- or herself to be a member of an oppressed minority group.
The other, somewhat subtler point, was that interface is very important. Sure, the MGB was a lousy car in almost every way that counted: balky, unreliable, underpowered. But it was fun to drive. It was responsive. Every pebble on the road was felt in the bones, every nuance in the pavement transmitted instantly to the driver’s hands. He could listen to the engine and tell what was wrong with it. The steering responded immediately to commands from his hands. To us passengers it was a pointless exercise in going nowhere—about as interesting as peering over someone’s shoulder while he punches numbers into a spreadsheet. But to the driver it was an experience. For a short time he was extending his body and his senses into a larger realm, and doing things that he couldn’t do unassisted.
The analogy between cars and operating systems is not half bad, and so let me run with it for a moment, as a way of giving an executive summary of our situation today.
Imagine a crossroads where four competing auto dealerships are situated. One of them (Microsoft) is much, much bigger than the others. It started out years ago selling three-speed bicycles (MS-DOS); these were not perfect, but they worked, and when they broke you could easily fix them.
There was a competing bicycle dealership next door (Apple) that one day began selling motorized vehicles—expensive but attractively styled cars with their innards hermetically sealed, so that how they worked was something of a mystery.
The big dealership responded by rushing a moped upgrade kit (the original Windows) onto the market. This was a Rube Goldberg contraption that, when bolted onto a three-speed bicycle, enabled it to keep up, just barely, with Apple-cars. The users had to wear goggles and were always picking bugs out of their teeth while Apple owners sped along in hermetically sealed comfort, sneering out the windows. But the Micro-mopeds were cheap, and easy to fix compared with the Apple-cars, and their market share waxed.
Eventually the big dealership came out with a full-fledged car: a colossal station wagon (Windows 95). It had all the aesthetic appeal of a Soviet worker housing block, it leaked oil and blew gaskets, and it was an enormous success. A little later, they also came out with a hulking off-road vehicle intended for industrial users (Windows NT), which was no more beautiful than the station wagon and only a little more reliable.
Since then there has been a lot of noise and shouting, but little has changed. The smaller dealership continues to sell sleek Euro-styled sedans and to spend a lot of money on advertising campaigns. They have had GOING OUT OF BUSINESS! signs taped up in their windows for so long that they have gotten all yellow and curly. The big one keeps making bigger and bigger station wagons and ORVs.
On the other side of the road are two competitors that have come along more recently.
One of them (Be, Inc.) is selling fully operational Batmobiles (the BeOS). They are more beautiful and stylish even than the Euro-sedans, better designed, more technologically advanced, and at least as reliable as anything else on the market—and yet cheaper than the others.
With one exception, that is: Linux, which is right next door, and which is not a business at all. It’s a bunch of RVs, yurts, tepees, and geodesic domes set up in a field and organized by consensus. The people who live there are making tanks. These are not old-fashioned, cast-iron Soviet tanks; these are more like the M1 tanks of the U.S. Army, made of space-age materials and jammed with sophisticated technology from one end to the other. But they are better than army tanks. They’ve been modified in such a way that they never, ever break down, are light and maneuverable enough to use on ordinary streets, and use no more fuel than a subcompact car. These tanks are being cranked out, on the spot, at a terrific pace, and a vast number of them are lined up along the edge of the road with keys in the ignition. Anyone who wants can simply climb into one and drive it away for free.
Customers come to this crossroads in throngs, day and night. Ninety percent of them go straight to the biggest dealership and buy station wagons or off-road vehicles. They do not even look at the other dealerships.
Of the remaining ten percent, most go and buy a sleek Euro-sedan, pausing only to turn up their noses at the philistines going to buy the station wagons and ORVs. If they even notice the people on the opposite side of the road, selling the cheaper, technically superior vehicles, these customers deride them as cranks and half-wits.
The Batmobile outlet sells a few vehicles to the occasional car nut who wants a second vehicle to go with his station wagon, but seems to accept, at least for now, that it’s a fringe player.
The group giving away the free tanks only stays alive because it is staffed by volunteers, who are lined up at the edge of the street with bullhorns, trying to draw customers’ attention to this incredible situation. A typical conversation goes something like this:
HACKER WITH BULLHORN: Save your money! Accept one of our free tanks! It is invulnerable, and can drive across rocks and swamps at ninety miles an hour while getting a hundred miles to the gallon!
PROSPECTIVE STATION WAGON BUYER: I know what you say is true . . .but . . .er . . .I don’t know how to maintain a tank!
BULLHORN: You don’t know how to maintain a station wagon either!
BUYER: "But this dealership has mechanics on staff. If something goes wrong with my station wagon, I can take a day off work, bring it here, and pay