The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Stephen Clark <sclark46@earthlink.net>
To: Adam Thornton <athornton@gmail.com>,
	Greg 'groggy' Lehey <grog@lemis.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] The Elements Of Style: UNIX As Literature
Date: Fri, 6 Nov 2020 12:26:13 -0500	[thread overview]
Message-ID: <3c54b19d-e604-68eb-2b4b-0b65e9cfb896@earthlink.net> (raw)
In-Reply-To: <5BE1CBD5-C9EB-45D4-B135-E58BCCCBE38C@gmail.com>

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.


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

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-05 22:10 Tyler Adams
2020-11-06  0:39 ` Kevin Bowling
2020-11-06  1:41 ` Larry McVoy
2020-11-06  5:04   ` John Cowan
2020-11-06  5:16     ` Steve Nickolas
2020-11-06  6:34     ` Rob Pike
2020-11-06 13:20       ` Will Senn
2020-11-06 15:07         ` Clem Cole
2020-11-06 15:40           ` Will Senn
2020-11-06 15:46             ` Chris Torek
2020-11-06 22:54               ` Greg 'groggy' Lehey
2020-11-06 23:29                 ` Steffen Nurpmeso
2020-11-06 22:31           ` Dave Horsfall
2020-11-06 23:41             ` Warren Toomey
2020-11-06  6:37     ` Greg 'groggy' Lehey
2020-11-06 15:06       ` Larry McVoy
2020-11-06 15:18         ` Bakul Shah
2020-11-06 15:19         ` Chris Torek
2020-11-06 16:46           ` Stephen Clark
2020-11-06 18:51         ` Jon Steinhart
2020-11-06 22:09           ` John Cowan
2020-11-06 22:44             ` Jon Steinhart
2020-11-06 22:12         ` Andy Kosela
2020-11-06 22:23           ` Larry McVoy
2020-11-07  0:16             ` Dave Horsfall
2020-11-08 23:23               ` George Michaelson
2020-11-06 17:05       ` Paul Winalski
2020-11-06 17:07         ` Larry McVoy
2020-11-06 17:25           ` Warner Losh
2020-11-06 17:13       ` Adam Thornton
2020-11-06 17:26         ` Stephen Clark [this message]
2020-11-06 18:24           ` John Cowan
2020-11-06 21:10   ` 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=3c54b19d-e604-68eb-2b4b-0b65e9cfb896@earthlink.net \
    --to=sclark46@earthlink.net \
    --cc=athornton@gmail.com \
    --cc=grog@lemis.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).