The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Stuff Received <stuff@riddermarkfarm.ca>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Early Unix and Keyboard Skills
Date: Thu, 3 Nov 2022 17:51:44 -0400	[thread overview]
Message-ID: <a5b9b6c4-de7d-3e7d-6c40-d1b3480fceef@riddermarkfarm.ca> (raw)
In-Reply-To: <CAKzdPgzm8fkT5SeAFf+uaesp-oti2UndDdTPiB8MRU3CPebfRw@mail.gmail.com>

On 2022-11-02 03:11, Rob Pike wrote:
> Neither ken nor dmr were impressive typists. In fact few programmers 
> were then, at least of my acquaintance.
>
> In the 1970s Bell Labs created the Getset - think of it as an early 
> wired smartphone, or a Minitel, with a little screen and keyboard. It 
> cost quite a bit but was a cool gadget so the executives all got one. 
> But, in fascinating contrast to the Blackberry a generation later, no 
> one would touch it - literally - because it had a keyboard, and 
> keyboards were for (female) secretaries, not (male) executives. The 
> product, although well ahead of its time, was a complete failure due 
> to the cultural bias then.
>
> There may be a good sociology paper in there somewhere.

I remember the dep't administrators having colour terminals connected to 
the mainframe, and all they did was look up the occasional telephone 
number, whilst the "secretaries" (as they were called then) being given 
b&w terminals for work.

> I'm not saying K&D shared this blinkered view, not at all, just that 
> typing skills were not de facto back then. Some of the folks were even 
> two-finger jabbers. I was a little younger and a faster typist than 
> most of the others, and I am not a good typist by any modern standard.
>
> 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.

I learnt in high school on a manual typewriter so I can appreciate 
that.  (Learning on a manual really builds up the muscles on one's 
little fingers. #6-)

N.

>
> -rob
>
> [...]

  parent reply	other threads:[~2022-11-03 21:52 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
2022-11-03 21:51     ` Stuff Received [this message]
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=a5b9b6c4-de7d-3e7d-6c40-d1b3480fceef@riddermarkfarm.ca \
    --to=stuff@riddermarkfarm.ca \
    --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).