The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] Is the Teletype the unsung hero of Unix?
Date: Sat, 26 Mar 2016 14:54:14 +1100	[thread overview]
Message-ID: <20160326035414.GJ3766@eureka.lemis.com> (raw)
In-Reply-To: <201603251443.u2PEh8OZ019856@skeeve.com>

On Friday, 25 March 2016 at 17:43:08 +0300, Aharon Robbins wrote:
>
> ...
>
> I certainly think there's some truth to this idea; longer command
> names and especially GNU style long options didn't appear until the
> video terminal era when terminals were faster (9600 or 19200 baud!)
> and much less physically demanding to use.  How MUCH correlation is
> there, I don't claim to know, but I think there's definitely some.

Certainly, but the question is whether it's enough to imply causality.
I am a very fast typer, but when we got our Tandem machines back in
1977, we discovered that the shell was called COMINT and the editor
was called EDIT.  Too long for my liking, so I shortened them to C and
E respectively, much to the disgust of the field technicians.  This
was long before I was exposed to Unix, and we were really happy with
our 9600 bps ADM-2s, so much faster than the IBM 3270s we had been
using on the /370.

Even now I tend to shorten file names.  And I suspect I'm not the only
person who hates these excessively long
--options-that-could-have-been-written-more-succinctly.  Probably it's
at least partially a mentality issue.

Greg
--
Sent from my desktop computer.
Finger grog at FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160326/b28eea17/attachment.sig>


  parent reply	other threads:[~2016-03-26  3:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-25 14:43 Aharon Robbins
2016-03-25 19:47 ` Jaap Akkerhuis
2016-03-25 21:03 ` Diomidis Spinellis
2016-03-28 20:12   ` scj
2016-04-01 14:06     ` Dave Horsfall
2016-04-01 22:41       ` Greg 'groggy' Lehey
2016-03-25 21:29 ` [TUHS] Command-line options Warren Toomey
2016-03-25 23:25   ` Greg 'groggy' Lehey
2016-03-26  2:10     ` John Cowan
2016-03-26  3:09       ` Charles Anthony
2016-03-26 19:43         ` Clem Cole
2016-03-26 20:54           ` Ronald Natalie
2016-03-26 22:05             ` John Cowan
2016-03-27  1:25             ` Dave Horsfall
2016-03-27  1:50               ` Charles Anthony
2016-03-27  2:01               ` Greg 'groggy' Lehey
2016-03-27  6:18                 ` Random832
2016-03-27  6:57                   ` Greg 'groggy' Lehey
2016-03-27 19:38                   ` Dave Horsfall
2016-03-27  1:35             ` Greg 'groggy' Lehey
2016-03-26  3:54 ` Greg 'groggy' Lehey [this message]
2016-03-26  4:30   ` [TUHS] Is the Teletype the unsung hero of Unix? Steve Nickolas
2016-03-26  5:44     ` Greg 'groggy' Lehey
2016-03-26  8:33       ` Steve Nickolas
     [not found] <mailman.1.1459562401.20104.tuhs@minnie.tuhs.org>
2016-04-02  2:17 ` Johnny Billquist
2016-04-02  2:35   ` Charles Anthony

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=20160326035414.GJ3766@eureka.lemis.com \
    --to=grog@lemis.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).