The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Rob Pike <robpike@gmail.com>
Cc: "Michael Kjörling" <e5655f30a07f@ewoof.net>, tuhs@tuhs.org
Subject: [TUHS] Re: Early Unix and Keyboard Skills
Date: Wed, 2 Nov 2022 09:28:38 -0400	[thread overview]
Message-ID: <CAC20D2MeDUf7OwUymSPZ7XE56ENn88XoCC8TMaxSvdJjhD4ADA@mail.gmail.com> (raw)
In-Reply-To: <CAKzdPgzm8fkT5SeAFf+uaesp-oti2UndDdTPiB8MRU3CPebfRw@mail.gmail.com>

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

On Wed, Nov 2, 2022 at 3:13 AM Rob Pike <robpike@gmail.com> wrote

> bwk was one who could smash out the text faster than many. His having
> learned on a teletype, the keyboard would resound with the impact of his
> forceful keystrokes.
>
Funny, I remember the first time I got to use something other than an ASR33
or an ASR28 sometime time in the early 1970s I think.    IIRC  It was a Tek
4010, but the memory at the time of being amazed that I did not need so
much energy to push the keys  and how quiet it was.  Before then I had
equated computing with the feel, sounds, and machine oil smells of Teletype
products. That said, when the VT52 came out in the mid-70s the DEC keyboard
on it was far from the feel of the IBM Selectric III - which was considered
the 'touch typist standard'
ᐧ

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

  reply	other threads:[~2022-11-02 13:30 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02  2:36 [TUHS] " steve jenkin
2022-11-02  6:53 ` [TUHS] " Michael Kjörling
2022-11-02  7:11   ` Rob Pike
2022-11-02 13:28     ` Clem Cole [this message]
2022-11-03 21:51     ` Stuff Received
2023-08-05 23:53     ` scj
2023-08-06  0:22       ` KenUnix
2023-08-06  0:43         ` Larry McVoy
2023-08-06 14:51           ` Leah Neukirchen
2023-08-06 15:01             ` Larry McVoy
2023-08-06 16:31             ` Clem Cole
2023-08-06 18:20               ` Jon Forrest
2023-08-07  4:56                 ` Adam Thornton
2023-08-06  8:37       ` Ronald Natalie
2022-11-02 12:13 ` Steffen Nurpmeso
2022-11-02 12:24   ` Steffen Nurpmeso
2022-11-02 20:35     ` Ron Natalie
2022-11-02 12:26   ` John P. Linderman
2022-11-02 13:07     ` Larry Stewart
2022-11-02 13:16       ` Larry McVoy
2022-11-02 13:27     ` Steffen Nurpmeso
2022-11-02 19:01 ` jason-tuhs
2022-11-02 19:20   ` John P. Linderman
2022-11-03  1:47     ` Ronald Natalie
2022-11-03  1:59       ` Dave Horsfall
2022-11-03  3:01       ` Clem Cole
2022-11-03 15:17       ` Paul Winalski
2022-11-03 16:18         ` Clem Cole
2022-11-03 17:02         ` John Cowan
2022-11-03 19:36           ` Rich Morin
2022-11-03 20:01             ` Charles H Sauer (he/him)
2022-11-02 12:16 Douglas 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=CAC20D2MeDUf7OwUymSPZ7XE56ENn88XoCC8TMaxSvdJjhD4ADA@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=e5655f30a07f@ewoof.net \
    --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).