The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Jon Steinhart <jon@fourwinds.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] The Elements Of Style: UNIX As Literature
Date: Fri, 06 Nov 2020 14:44:14 -0800	[thread overview]
Message-ID: <202011062244.0A6MiEgX575756@darkstar.fourwinds.com> (raw)
In-Reply-To: <CAD2gp_RnZbUCahqfWzuyOBR8fpbZTNw5aQDQhNGdbQ1z4pfSRw@mail.gmail.com>

John Cowan writes:
> On Fri, Nov 6, 2020 at 1:51 PM Jon Steinhart <jon@fourwinds.com> wrote:
>
> > I've always been willing to spend buckets of money on the monitors because
> > to me that's an area where bigger and higher resolution is always better.
>
> You'd hardly want one the size of a city block, or even of a room wall.
>
> > I hated Shakespeare in high school.  One of the big reasons was that I felt
> > that he made up a word whenever he didn't have a good one available.
>
> Contrary to Internet opinion, Shakespeare probably never invented any
> words.  At most he is the first person to record in writing a word whose
> written works have survived (mostly).  Why would a commercial playwright
> (and Shakespeare wrote for money) use a word his audience didn't
> understand?   They'd boo the play off the stage, with or without rotten
> fruit.  He did both invent and reuse a lot of phrases: see <
> https://inside.mines.edu/~jamcneil/levinquote.html>, or google for "you are
> quoting Shakespeare".
>
> The
> > flipping back and forth to the list of definitions completely interrupted
> > the cadence of reading.
>
> Pop-up translations would be much better, of course.  I studied R&J with
> footnotes; my daughter, with an across-the-page translation into
> Contemporary Modern English.  Of course, that meant I had to explain some
> of the gallows humor to her, like Mercutio's dying words: "Seek for me
> tomorrow, and you will find me a *grave* man."
>
> > While readers might "lose focus" part of the way through long lines, that
> > has to
> > be balanced against the loss of focus that comes from 'mental
> > carriage-returns"
> > when text is too narrow and broken across several lines.  Again, not
> > studied as
> > far as I know.
>
> Lispers, of course, have only one kind of bracket, and append as many
> close-brackets to each line as are needed there.  (We don't count them,
> Emacs and vi do the matching.)  Sure saves on vertical whitespace, which
> means you typically can see a whole function in one screen.

As I said in my original post, we're getting into religion here.

So we have different views on monitors; I am contemplating replacing my 32"
UHD monitor with a 70" UHD TV.  Why?  Because I can keep everything on my
screen the same which will make everything bigger so I can put the monitor
farther away getting me out of my farsighted zone and into my 20-20 range
which would eliminate the need for glasses.

Not gonna rathole on the Shakespeare analogy - maybe I'm wrong but it's
not relevant to the point that I was making.  The books that we were given
in high school didn't have pop-up translations or footnotes.

In case I wasn't clear in my original posting, the topic was mental locality
of reference issues as related to terminal size and coding style.

Jon

  reply	other threads:[~2020-11-06 22:45 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 [this message]
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=202011062244.0A6MiEgX575756@darkstar.fourwinds.com \
    --to=jon@fourwinds.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).