The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Henry Bent <henry.r.bent@gmail.com>
To: Rob Pike <robpike@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Origins and life of the pg pager
Date: Mon, 15 Jun 2020 18:55:40 -0400	[thread overview]
Message-ID: <CAEdTPBfKKDWEOn4Mb5uCFu7ksm_ghQ_LXTbZcssyUuq0c8s2Ew@mail.gmail.com> (raw)
In-Reply-To: <CAKzdPgy07hwixLdUAqLyS9iZLxbn1h=YwntZt78uKeYvyOtEQw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]

On Mon, 15 Jun 2020 at 17:37, Rob Pike <robpike@gmail.com> wrote:

> I had forgotten about that tool, along with many others. "Comp" sounds
> plausible but as I said, I forget. (Not a sign of age; my memory for
> details is no match for Clem's; to me stage actors are superheroes).
>

Remembering the blocking and the actor's names for a play you saw thirty
years ago would be an impressive feat, but I would argue that it is much
more beneficial in the long run to remember the basic plot and the message
that the production was attempting to convey.

> This history stuff is fun because of the reminder of a time when tools
were simple and you could create a whole new one in an afternoon.

Indeed, that's a nearly impossible task now.  We have transitioned to a
world where you can say, "here's my sketch for a program that I think would
be useful," and that sketch is either a basic chapter outline or you've
only finished writing chapter one.  You put it up on Github, try to give it
a little publicity, and hope that others can share your vision or at least
provide constructive criticism.

-Henry

[-- Attachment #2: Type: text/html, Size: 1537 bytes --]

  reply	other threads:[~2020-06-15 22:56 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15 20:25 Norman Wilson
2020-06-15 21:36 ` Rob Pike
2020-06-15 22:55   ` Henry Bent [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-06-15  2:26 Doug McIlroy
2020-06-15  2:41 ` Bakul Shah
2020-06-15  2:55   ` Larry McVoy
2020-06-15  4:26     ` Rob Pike
2020-06-15  4:27     ` Bakul Shah
2020-06-15  4:38       ` George Michaelson
2020-06-15  7:40     ` Ed Carp
2020-06-15  8:17       ` Rob Pike
2020-06-15  7:12   ` Thomas Paulsen
2020-06-14 22:52 [TUHS] Fwd: " Warren Toomey
2020-06-14 23:37 ` Mary Ann Horton
2020-06-14 23:52   ` [TUHS] " David Barto
2020-06-15  0:06     ` George Michaelson
2020-06-15  0:31     ` Alan D. Salewski
2020-06-15  0:35       ` Alan D. Salewski
2020-06-15  1:38         ` Warner Losh
2020-06-15  1:47           ` Larry McVoy
2020-06-15  2:38             ` Alec Muffett
2020-06-15  2:46               ` Alec Muffett
2020-06-15  2:26           ` Charles H. Sauer
2020-06-15 14:03           ` Mary Ann Horton
2020-06-15 20:19             ` Greg A. Woods
2020-06-15 20:50               ` Mary Ann Horton
2020-06-15  5:41   ` [TUHS] Fwd: " Lars Brinkhoff
2020-06-15 13:56     ` Clem Cole
2020-06-15 14:15       ` Mary Ann Horton
2020-06-15 14:56         ` Clem Cole
2020-06-21 18:49           ` Michael Siegel
2020-06-22  0:35             ` Greg A. Woods
2020-06-22 16:24               ` Derek Fawcus
2020-06-22 21:33                 ` Rob Pike
2020-06-22 21:59                   ` [TUHS] " Bakul Shah
2020-06-22 22:43                     ` Steffen Nurpmeso
2020-06-25  1:50                       ` Theodore Y. Ts'o
2020-06-25 21:31                         ` Steffen Nurpmeso
2020-07-05  1:34                         ` Dave Horsfall

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=CAEdTPBfKKDWEOn4Mb5uCFu7ksm_ghQ_LXTbZcssyUuq0c8s2Ew@mail.gmail.com \
    --to=henry.r.bent@gmail.com \
    --cc=robpike@gmail.com \
    --cc=tuhs@tuhs.org \
    /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).