The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: crossd@gmail.com (Dan Cross)
Subject: [TUHS] 80 columns ...
Date: Wed, 8 Nov 2017 16:34:13 -0500	[thread overview]
Message-ID: <CAEoi9W7xmMU7OWgVDGbdMP9P6MFYXzD_c8YH+hEocMhniAfsjQ@mail.gmail.com> (raw)
In-Reply-To: <20171108212424.GA15911@mcvoy.com>

On Wed, Nov 8, 2017 at 4:24 PM, Larry McVoy <lm at mcvoy.com> wrote:
> On Wed, Nov 08, 2017 at 04:19:49PM -0500, Dan Cross wrote:
>> On Wed, Nov 8, 2017 at 4:02 PM, Larry McVoy <lm at mcvoy.com> wrote:
>> > On Wed, Nov 08, 2017 at 08:52:03PM +0000, ron minnich wrote:
>> >> So, 80 column folks, would you find this
>> >> a(b,
>> >> c,
>> >> d)
>> >>
>> >> more readable than
>> >> a(b,c,d)
>> >
>> > yeah, I do.  I work on thinkpad x220 sized machines which are just big enough
>> > for two 80 column windows with a little left over.  When I'm checking in code,
>> > reviewing code, debugging code, I frequently want to see two versions of the
>> > same file side by side.  If you code wider than 80 columns it greatly reduces
>> > the speed at which you can figure out what happened.
>>
>> The thing that sort of vexes me about these arguments is that the
>> number 80 is so arbitrary.
>
> Not really.  Programmers need windows side by side.  Lots and lots of bit
> mapped displays can handle 2 80 column windows at a reasonable font size.

Lots of them can also handle two 100 column windows, or perhaps more
realistically 82- or 85-column windows, but here's the thing that I
don't buy about that argument: if given a large enough screen,
proponents would claim that they needed 3 side-by-side windows instead
of two. As a simple test, I can put two 100x75 windows side-by-side on
my desktop here at work, using a font size big enough for my
deteriorating eyesight. I can fit three 80x75 windows next to one
another, but I can fit *4* 60-column windows next to each other.

> And I made the point about side by side diff tools.

But what about 3-way merge tools?

> And I made the point about being able to read down the center and get the
> rest through peripheral vision.
>
> Would I like wider?  Not really, at this point the vast majority of the
> code I look at, the man pages and other docs I look, they all fit in 80
> columns.  Sure, you could pick something else but you are just fighting
> reality.
>
> It's like video on phones.  We still call it taping.  Probably still will
> in a 100 years.  Where's the tape?  In history.

Language is a funny thing. Well, I better get back in the saddle and
write some code.

        - Dan C.


  parent reply	other threads:[~2017-11-08 21:34 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-08 20:52 ron minnich
2017-11-08 21:02 ` Larry McVoy
2017-11-08 21:19   ` Dan Cross
2017-11-08 21:24     ` Larry McVoy
2017-11-08 21:28       ` Steve Nickolas
2017-11-08 21:48         ` [TUHS] (cassette) tape coming back [was " Charles H Sauer
2017-11-08 22:46           ` Don Hopkins
2017-11-08 23:28         ` [TUHS] " Dave Horsfall
2017-11-08 23:35           ` Ron Natalie
2017-11-08 23:39             ` Dave Horsfall
2017-11-08 21:34       ` Dan Cross [this message]
2017-11-08 21:40         ` Dan Cross
2017-11-08 21:40         ` Larry McVoy
2017-11-08 21:43           ` Dan Cross
2017-11-09  1:00             ` Theodore Ts'o
2017-11-08 23:46     ` Steffen Nurpmeso
2017-11-09  6:52       ` Otto Moerbeek
2017-11-08 21:06 ` Bakul Shah
2017-11-08 21:18   ` Steve Nickolas
2017-11-08 22:17 ` Grant Taylor
2017-11-08 22:30   ` Arthur Krewat
2017-11-08 23:07     ` Andy Kosela
2017-11-08 23:15       ` Arthur Krewat
2017-11-08 23:15         ` Warner Losh
2017-11-08 23:49           ` Arthur Krewat
2017-11-09  0:04             ` Dave Horsfall
2017-11-08 23:24         ` Andy Kosela
2017-11-09  7:24 ` Lars Brinkhoff
2017-11-09 15:02   ` Don Hopkins
2017-11-09 19:14     ` Ron Natalie
2017-11-10 16:18       ` Nemo
2017-11-10 19:05         ` Jon Steinhart
2017-11-10 20:36           ` Toby Thain
2017-11-10 20:39             ` Larry McVoy
2017-11-10 20:46               ` Warner Losh
2017-11-10 20:59                 ` Larry McVoy
2017-11-11  9:24                 ` David Arnold
2017-11-10 20:43             ` Jon Steinhart
2017-11-10 20:58               ` Larry McVoy
2017-11-10 21:02                 ` Jon Steinhart
2017-11-10 21:09                   ` Larry McVoy
2017-11-10 21:12                     ` Jon Steinhart
2017-11-10 21:34                       ` William Corcoran
2017-11-10 21:50                         ` Jon Steinhart
2017-11-10 22:58                         ` Dave Horsfall
2017-11-10 23:05                           ` Jon Steinhart
2017-11-10 23:52                             ` Toby Thain
2017-11-11  0:24                             ` Larry McVoy
2017-11-11 16:40                   ` Ian Zimmerman
2017-11-11 16:47                     ` Larry McVoy
2017-11-11 17:23                       ` Jon Steinhart
2017-11-11 17:38                         ` Ralph Corderoy
2017-11-10 22:46               ` Toby Thain
2017-11-10 22:59                 ` Jon Steinhart
2017-11-11 14:33                   ` Andy Kosela
2017-11-11 17:19                     ` Jon Steinhart
2017-11-11 17:24                       ` Larry McVoy
2017-11-11 17:25                         ` Jon Steinhart
2017-11-10 23:59           ` Don Hopkins
2017-11-10 22:10         ` Dave Horsfall
2017-11-09 20:46     ` Lars Brinkhoff
2017-11-10 17:21 Norman Wilson
2017-11-10 17:56 ` Larry McVoy
2017-11-11 17:04 ` Ian Zimmerman
2017-11-11 17:30   ` Random832
2017-11-11 18:05     ` Ian Zimmerman

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=CAEoi9W7xmMU7OWgVDGbdMP9P6MFYXzD_c8YH+hEocMhniAfsjQ@mail.gmail.com \
    --to=crossd@gmail.com \
    /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).