The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: 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 07:06:09 -0800	[thread overview]
Message-ID: <20201106150609.GR26296@mcvoy.com> (raw)
In-Reply-To: <20201106063725.GB99027@eureka.lemis.com>

On Fri, Nov 06, 2020 at 05:37:25PM +1100, Greg 'groggy' Lehey wrote:
> On Friday,  6 November 2020 at  0:04:28 -0500, John Cowan wrote:
> > On Thu, Nov 5, 2020 at 8:41 PM Larry McVoy <lm@mcvoy.com> wrote:
> >
> >> I click but I mostly live in terminal windows.  Which are all 80
> >> columns because that's the right width (I can go on and on about
> >> that).
> >
> > Aw, c'mon.  You're going to tell us that the number of punch holes
> > that IBM could fit on a punch card in 1928 that was exactly the size
> > of the dollar bill used in the U.S. from 1862 to 1923 so that it
> > could be stored in a mechanical cash register is miraculously the
> > Right Thing when it comes to reading monospaced text on a screen?
> 
> I think you're jumping to conclusions.  The importance of 80
> characters (for small values of 80) is that it's a comfortable text
> width for human eyes.  

Exactly this.  I'm a very fast reader, easily 2-3x the average.  I read by
running my eyes down the middle of the page and get the left and right
from peripheral vision.  It's super fast but it doesn't work when you
get much bigger than 80 columns.

Even if you read normally, the wider it is, the more back and forth your
eyes do so less is more.

It's also why I'm fine with smaller screens, I tried the giant apple
displays and found that those required head movement along with eye
movement.

I'm lazy.

  reply	other threads:[~2020-11-06 15:06 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 [this message]
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
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=20201106150609.GR26296@mcvoy.com \
    --to=lm@mcvoy.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).