The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: Andy Kosela <akosela@andykosela.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] The Elements Of Style: UNIX As Literature
Date: Fri, 6 Nov 2020 14:23:02 -0800	[thread overview]
Message-ID: <20201106222302.GG26411@mcvoy.com> (raw)
In-Reply-To: <CALMnNGg=9KHCwqaqdFESBQr=Ru_qzM=x-S2fc=ewgJNf2zLRFQ@mail.gmail.com>

On Fri, Nov 06, 2020 at 11:12:23PM +0100, Andy Kosela wrote:
> The 70s, 80s and 90s got a lot of things right.  The introduction
> of widescreen LCD monitors around 2007 ruined a lot of things.

Yeah, I wasn't a fan of going wider.  I'm bucking the old school trend
and typing on an 80x44 terminal which is as tall as I can go on my X1
Carbon.  It's big enough.

For me, taller is more useful than wider, provided I can get about 162
columns so I can do side by side diffs.  More than that doesn't do much
for me.

But I'm pretty old school, I write in C, I debug a lot with printf and
asserts, I'm kind of a dinosaur.  In the last year or so I reconnected
with Kirk and Eric and much to my surprise, and pleasure, I found that
Eric and I see things very similarly, I'd be happy to work with/for that
guy, we really agree.

One thing I will say about big monitors is they are great for photos.
I do a lot of digital photography and have no desire to go back to 
black & white or CRT terminals.

  reply	other threads:[~2020-11-06 22:24 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 [this message]
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=20201106222302.GG26411@mcvoy.com \
    --to=lm@mcvoy.com \
    --cc=akosela@andykosela.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).