From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] 80 columns ...
Date: Fri, 10 Nov 2017 12:59:20 -0800 [thread overview]
Message-ID: <20171110205920.GC29606@mcvoy.com> (raw)
In-Reply-To: <CANCZdfruju317QTVn8piifh4UqyWON4Xht_KLt-_NVPEAUp3NA@mail.gmail.com>
On Fri, Nov 10, 2017 at 01:46:30PM -0700, Warner Losh wrote:
> On Fri, Nov 10, 2017 at 1:39 PM, Larry McVoy <lm at mcvoy.com> wrote:
>
> > > > Separate from this, I think that the whole 80 column thing is a bit
> > silly.
> > > > I have used 132 as by default for a long time now.
> > >
> > > Just don't move on without some limit. There are real
> > > cognitive/typographic reasons why excessively long lines hurt
> > > comprehension. This is why both 500 year old books and 5 month old books
> > > have narrow measures.
> >
> > I've made that point and people blithely ignore it.
> >
>
> When I was debating style wars in the 90's, we adopted a 'wide is OK'
> approach, but with a soft limit of ~130 and a hard limit of 160 in
> exceptional cases. There was some research that showed that there's a
> limited field of view you want to be able to look at the code without
> moving your eyes side to side, just up and down. With the technology of the
> time, above about 130 would be hard to read 'at a glance'. Years later, I
> went looking for those studies, and couldn't find them and the original
> advocate of the view couldn't provide them.
>
> I'm the first to admit that 80 is too few. But 200 is definitely too wide
> and 100-120 seems to still be the sweet spot for my eyes and the range of
> hardware that I use.
I could live with 100.
next prev parent reply other threads:[~2017-11-10 20:59 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
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 [this message]
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=20171110205920.GC29606@mcvoy.com \
--to=lm@mcvoy.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).