In the Beginning...Was the Command Line

In the Beginning...Was the Command Line Read Free

Book: In the Beginning...Was the Command Line Read Free
Author: Neal Stephenson
Ads: Link
to do when writing a new piece of software is to figure out how to take the information that is being worked with (in a graphics program, an image; in a spreadsheet, a grid of numbers) and turn it into a linear string of bytes. These strings of bytes are commonly called files or (somewhat more hiply) streams. They are to telegrams what modern humans are to Cro-Magnon man, which is to say, the same thing under a different name. All that you see on your computer screen—your Tomb Raider, your digitized voice mail messages, faxes, and word-processing documents written in thirty-seven different typefaces—is still, from the computer’s point of view, just like telegrams, except much longer and demanding of more arithmetic.
    The quickest way to get a taste of this is to fire up your web browser, visit a site on the Net, and then select the View/Document Source menu item. You will get a bunch of computer code that looks something like this:
     
    
     
    
     
     C R Y P T O N O M I C O N
     
    
     
    
     
    
    
    
    
    
    
    
     
    

     
    

    
     
    
     
    
     
    
     
    
     
    This crud is called HTML (HyperText Markup Language) and it is basically a very simple programming language instructing your web browser how to draw a page on a screen. Anyone can learn HTML and many people do. The important thing is that no matter what splendid multimedia web pages they might represent, HTML files are just telegrams.
    When Ronald Reagan was a radio announcer, he used to call baseball games that he did not physically attend by reading the terse descriptions that trickled in over the telegraph wire and were printed out on a paper tape. He would sit there, all by himself in a padded room witha microphone, and the paper tape would creep out of the machine and crawl over the palm of his hand printed with cryptic abbreviations. If the count went to three and two, Reagan would describe the scene as he saw it in his mind’s eye: “The brawny left-hander steps out of the batter’s box to wipe the sweat from his brow. The umpire steps forward to sweep the dirt from home plate,” and so on. When the cryptogram on the paper tape announced a base hit, he would whack the edge of the table with a pencil, creating a little sound effect, and describe the arc of the ball as if he could actually see it. His listeners, many of whom presumably thought that Reagan was actually at the ballpark watching the game, would reconstruct the scene in their minds according to his descriptions.
    This is exactly how the World Wide Web works: the HTML files are the pithy description on the paper tape, and your web browser is Ronald Reagan. The same is true of graphical user interfaces in general.
    So an OS is a stack of metaphors and abstractions that stands between you and the telegrams, and embodying various tricks the programmer used to convert the information you’re working with—be it images, e-mail messages, movies, or word-processing documents—into the necklaces of bytes that are the only things computers know how to work with. When we used actual telegraph equipment (teletypes) or their higher-tech substitutes (“glass teletypes,” or the MS-DOS command line) to work with our
© ReadFree 2024 [email protected]

    
    

    Cryptonomincon by Neal Stephenson