<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:dc="https://purl.org/dc/elements/1.1/" xmlns:content="https://purl.org/rss/1.0/modules/content/" xmlns:foaf="https://xmlns.com/foaf/0.1/" xmlns:og="https://ogp.me/ns#" xmlns:rdfs="https://www.w3.org/2000/01/rdf-schema#" xmlns:schema="https://schema.org/" xmlns:sioc="https://rdfs.org/sioc/ns#" xmlns:sioct="https://rdfs.org/sioc/types#" xmlns:skos="https://www.w3.org/2004/02/skos/core#" xmlns:xsd="https://www.w3.org/2001/XMLSchema#" version="2.0" xml:base="https://www.linuxjournal.com/tag/neal-stephenson">
  <channel>
    <title>Neal Stephenson</title>
    <link>https://www.linuxjournal.com/tag/neal-stephenson</link>
    <description/>
    <language>en</language>
    
    <item>
  <title>In the End Is the Command Line</title>
  <link>https://www.linuxjournal.com/content/end-command-line</link>
  <description>  &lt;div data-history-node-id="1340687" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-field-node-image field--type-image field--label-hidden field--item"&gt;  &lt;img src="https://www.linuxjournal.com/sites/default/files/nodeimage/story/Neal-Stephenson-in-the-beginning_0.jpg" width="620" height="310" alt="Neal Stephenson's In the Beginning Was the Command Line" typeof="foaf:Image" class="img-responsive" /&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/doc-searls" lang="" about="https://www.linuxjournal.com/users/doc-searls" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Doc Searls&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;&lt;em&gt;Times have changed every character but one in Neal Stephenson's classic. That one is
Linux.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;
I was wandering through &lt;a href="https://www.keplers.com/"&gt;Kepler&lt;/a&gt;'s, the &lt;a href="https://en.wikipedia.org/wiki/Kepler%27s_Books"&gt;legendary bookstore&lt;/a&gt;, sometime late in 1999, when
I spotted a thin volume with a hard-to-read title on the new book table. &lt;em&gt;In the
Beginning...Was the Command Line&lt;/em&gt;, the cover said.
&lt;/p&gt;

&lt;p&gt;
The command line was new to me when I started writing for &lt;em&gt;Linux Journal&lt;/em&gt; in 1996. I
hadn't come from UNIX or from programming. My tech background was in ham radio and
broadcast engineering, and nearly all my hacking was on RF hardware. It wasn't a joke
when I said the only code I knew was Morse. But I was amazed at how useful and
necessary the command line was, and I was thrilled to see &lt;a href="https://en.wikipedia.org/wiki/Neal_Stephenson"&gt;Neal Stephenson&lt;/a&gt; was the author
of that book.
(Pro tip: you can tell the commercial worth of an author by the size of his or her name
on the cover. If it's bigger than the title of the book, the writer's a big deal.
Literally.)
&lt;/p&gt;

&lt;p&gt;
So I bought it, and then I read it in one sitting. You can do the same. In fact, I command
that you do, if you haven't already, because (IMHO) it's the most classic book ever
written about both the command line and Linux itself—a two-fer of the first order.
&lt;/p&gt;

&lt;p&gt;
And I say this in full knowledge (having re-read the whole thing many times, which is
easy, because it's short) that much of what it brings up and dwells on is stale in the
extreme. The MacOS and the Be operating systems are long gone (and the Be computer was
kind of dead on arrival), along with the Windows of that time. Today Apple's OS X is BSD
at its core, while Microsoft produces lots of open-source code and contributes mightily
to The Linux Foundation. Some of Neal's observations and complaints about computing and
the culture of the time also have faded in relevance, although some remain enduringly
right-on. (If you want to read a section-by-section critique of the thing, &lt;a href="https://garote.bdmonkeys.net/"&gt;Garrett
Birkel&lt;/a&gt; &lt;a href="https://garote.bdmonkeys.net/commandline/index.html"&gt;produced
one&lt;/a&gt; in the mid-2000s with &lt;a href="https://garote.bdmonkeys.net/commandline/permission.html"&gt;Neal's permission&lt;/a&gt;. But do read the book
first.)
&lt;/p&gt;

&lt;p&gt;
What's great about &lt;em&gt;Command Line&lt;/em&gt; is how well it explains the original virtues of UNIX,
and of Linux as the operating system making the most of it:
&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;
The file systems of Unix machines all have the same general structure. On your
flimsy operating systems, you can create directories (folders) and give them names like
Frodo or My Stuff and put them pretty much anywhere you like. But under Unix the
highest level—the root—of the filesystem is always designated with the
single character "/" and it always contains the same set of top-level directories:
&lt;/p&gt;&lt;/blockquote&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/end-command-line" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Wed, 03 Jul 2019 11:30:00 +0000</pubDate>
    <dc:creator>Doc Searls</dc:creator>
    <guid isPermaLink="false">1340687 at https://www.linuxjournal.com</guid>
    </item>

  </channel>
</rss>
