Computer Old Farts Forum
 help / color / mirror / Atom feed
From: clemc at ccc.com (Clem Cole)
Subject: [COFF] [TUHS] The Elements Of Style: UNIX As Literature
Date: Fri, 6 Nov 2020 12:56:05 -0500	[thread overview]
Message-ID: <CAC20D2Pncr6G2ZoouOpZBgxpdLzbPEo__T2kiRVY8svnpHm1TA@mail.gmail.com> (raw)
In-Reply-To: <3c54b19d-e604-68eb-2b4b-0b65e9cfb896@earthlink.net>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1829 bytes --]

I'd be curious to hear from the folks a few years older than I (I started
in the later 60s with the GE-635), but my own experiences of having lived
through some of it, I personally think it was more to do with all of the
systems of the time switching from cards to the Model 28 and later the 33
then Unix or AT&T.  Unix was just one of the systems that we used at the
time of the transition from cards.  But the other timesharing systems of
those days began to transition to the tty's requirements.

On Fri, Nov 6, 2020 at 12:27 PM Stephen Clark <sclark46 at earthlink.net>
wrote:

> On 11/6/20 12:13 PM, Adam Thornton wrote:
> > I’m going to chime in on pro-80-columns here, because with the text a
> comfortable size to read (although this is getting less true as my eyes
> age), I can read an entire 80-column line without having to sweep my eyes
> back and forth.
> >
> > I can’t, and never could, do that at 132.
> >
> > As a consequence, I read much, much faster with 80-column-ish text
> blocks.
> >
> > I also think there is something to the “UNIX is verbal” and “UNIX nerds
> tend to be polyglots often with a surprising amount of liberal arts
> background of one kind or another,” argument.  That may, however, merely be
> confirmation bias.
> >
> > Adam
> May have had to do with the first terminal commonly used with UNIX.
>
> The Model 33 printed on 8.5-inch (220 mm) wide paper, supplied on
> continuous
> 5-inch (130 mm) diameter rolls and fed via friction (instead of, e.g.,
> tractor
> feed). It printed at a fixed 10 characters per inch, and supported
> 74-character
> lines,[13] although 72 characters is often commonly stated.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20201106/d131a070/attachment.htm>


       reply	other threads:[~2020-11-06 17:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEuQd1AWs=jpHYk3nGpKsBV=qF4DZVXvXzynSeDK5S-r-hfryw@mail.gmail.com>
     [not found] ` <20201106014109.GP26296@mcvoy.com>
     [not found]   ` <CAD2gp_Q-wTvG2cAW5goJFYW3A6qF9zOuTh=Y4Kahh0nLBtof2Q@mail.gmail.com>
     [not found]     ` <20201106063725.GB99027@eureka.lemis.com>
     [not found]       ` <5BE1CBD5-C9EB-45D4-B135-E58BCCCBE38C@gmail.com>
     [not found]         ` <3c54b19d-e604-68eb-2b4b-0b65e9cfb896@earthlink.net>
2020-11-06 17:56           ` clemc [this message]
     [not found]       ` <20201106150609.GR26296@mcvoy.com>
     [not found]         ` <202011061519.0A6FJOAx034308@elf.torek.net>
2020-11-06 23:08           ` grog
     [not found]         ` <CALMnNGg=9KHCwqaqdFESBQr=Ru_qzM=x-S2fc=ewgJNf2zLRFQ@mail.gmail.com>
     [not found]           ` <20201106222302.GG26411@mcvoy.com>
2020-11-07  0:16             ` dave
     [not found]     ` <CAKzdPgx1Ptu=sahO3o5KYS-A=vnfXK-hs=QeVwO_Vd1cFfaeqw@mail.gmail.com>
     [not found]       ` <a588c934-e403-2a4e-4701-669b8c14e989@gmail.com>
     [not found]         ` <CAC20D2PPw3Ua3-VpMYjh=NaC09=9Q528kqEvE7SvmO3Ly2JO0A@mail.gmail.com>
     [not found]           ` <175409f6-af94-601e-3db3-a5af5d7f64d0@gmail.com>
2020-11-06 15:53             ` clemc
2020-11-06 19:22               ` tytso
2020-11-06 19:24                 ` clemc
2020-11-06 22:58               ` grog
2020-11-07 21:04                 ` clemc
2020-11-07 23:05                   ` dave
2020-11-09  4:36                   ` [COFF] Daisy wheel printers (was: [TUHS] The Elements Of Style: UNIX As Literature) grog
2020-11-09 14:26                     ` clemc
2020-11-10  0:10                       ` grog
2020-11-10 14:48                         ` clemc
2020-11-10 15:10                           ` stewart
2020-11-09 22:08                     ` dave
2020-11-10  0:48                       ` grog
     [not found]             ` <202011061546.0A6Fkv3D034443@elf.torek.net>
2020-11-06 16:22               ` [COFF] [TUHS] The Elements Of Style: UNIX As Literature clemc
2020-11-06 18:12                 ` torek
2020-11-07  2:52                 ` cym224
     [not found]               ` <20201106225422.GD99027@eureka.lemis.com>
     [not found]                 ` <20201106232901.AkY2I%steffen@sdaoden.eu>
2020-11-07  4:22                   ` grog
2020-11-07 20:31                     ` steffen
2020-11-11  8:31           ` [COFF] " peter
2020-11-11 12:21             ` tih
2020-11-11 21:09             ` dave

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=CAC20D2Pncr6G2ZoouOpZBgxpdLzbPEo__T2kiRVY8svnpHm1TA@mail.gmail.com \
    --to=coff@minnie.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).