The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: rminnich@gmail.com (ron minnich)
Subject: [TUHS] How Unix brings people together, or it's a small world
Date: Mon, 06 Feb 2017 16:42:11 +0000	[thread overview]
Message-ID: <CAP6exYLNg5uiog362OSdEcL0VbueS=Q5tnxfqzK0asubHmj5gg@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.20.1702060857070.46495@aneurin.horsfall.org>

On Sun, Feb 5, 2017 at 2:11 PM Dave Horsfall <dave at horsfall.org> wrote:

>
>
> Unix itself pretty much changed the world; without those two bods we'd all
> be running M$ Windoze, and believing that it's wonderful ('cuz Billy told
> us so).
>
> --
>


yes and no. Yes, because the ideas made it out. No, because, well ...

In 1976 or so bwk came to udel as we had just set up a Unix V6 at that
point.

He gave a great talk. One example was looking up all the words in the
dictionary that could be created with the upside down characters form a
calculator (left as an exercise for the reader).

He ran a standard dictionary tool, and pointed out that
o it could not run in a pipe
o it had a prompt, meaning even if run in a pipe there'd be output we did
   not wan
o it was wordy, telling us "when it was compiled (like we care) ..."

I always loved that 'like we care" part.

he pointed out the core concept: small simple tools that do one thing well,
and that you compose with | operators.

What a long strange trip it's been. Lots of commands are now little shells:
git --help
go help
bash --help

and many interns I now work with are astonished when I point out that bash
can be part of a processing pipeline.

Further, back then, processes were cheap. You used them and tossed them. I
saw a talk a few years back about why you should use i3 instead of wmii;
one reason was that starting processes was so expensive that i3 did things
much faster (this is actually true now; people tell me all the time how
expensive it is to start a process).

Why are process slow to start?
LD_DEBUG=all date
strace date and count the system calls

"modern" software techniques have completely forgotten all the lessons of
Unix. It's been sad to watch. Linux today is much more like the systems
Unix displaced than it is like Unix. So, yes, the world changed, but not as
much as we might think. Meet the new boss, same as the old boss.

ron
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170206/9d175fef/attachment.html>


  parent reply	other threads:[~2017-02-06 16:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.182.1485985948.3779.tuhs@minnie.tuhs.org>
2017-02-02 17:57 ` David
2017-02-05 22:10   ` Dave Horsfall
2017-02-06 16:07     ` Jason Stevens
2017-02-06 16:42     ` ron minnich [this message]
2017-02-03  4:04 Doug McIlroy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAP6exYLNg5uiog362OSdEcL0VbueS=Q5tnxfqzK0asubHmj5gg@mail.gmail.com' \
    --to=rminnich@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).