From: jon@fourwinds.com (Jon Steinhart)
Subject: [TUHS] 80 columns ...
Date: Fri, 10 Nov 2017 13:02:55 -0800 [thread overview]
Message-ID: <201711102102.vAAL2tM6024205@darkstar.fourwinds.com> (raw)
In-Reply-To: <20171110205806.GB29606@mcvoy.com>
Larry McVoy writes:
> On Fri, Nov 10, 2017 at 12:43:36PM -0800, Jon Steinhart wrote:
> > Toby Thain writes:
> > > 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.
> > >
> > > 80 might be too narrow for most, but at some point beyond 132 is "too
> > > far". :)
> >
> > Well, I would claim that books have technological limitations that are
> > different than computer monitors. It's a matter of doing what's appropriate
> > instead of taking a dogmatic approach.
> >
> > I will point out that while it's sometimes a pain, the reader/writer ratio
> > is a major driving force. I save on typing and use very terse code when
> > writing stuff for myself. But, when writing stuff where there are many
> > readers I feel that it's my job to put in the extra work to make it more
> > accessible to the reader, partly because I don't want the readers bugging me.
>
> So for the Nth time, there are people who read, I'm one of them,
> by looking down the middle of the text and getting the rest through
> peripheral vision. I read easily 3-4x faster than a decently fast reader
> and I get enough info that I can find the place where I need to go read
> more closely later.
>
> I can't imagine I'm the only person who does this, I'm special but not
> that special :) So for me, wider is optimizing me out, not optimizing
> for me.
Well, as someone who also reads I don't really understand how your point
relates to 80 columns. It sounds to me that you're making an argument
for something else in which I strongly believe, which is that the block
structure of the code should be clearly visible so that a reader doesn't
have to read every line in order to understand what's going on. As an
example, I abhor styles that say that continuations of long lines should
be indented either an extra tab or right-aligned with the first line.
Both of those styles break the visible block structure.
Jon
next prev parent reply other threads:[~2017-11-10 21:02 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
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 [this message]
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=201711102102.vAAL2tM6024205@darkstar.fourwinds.com \
--to=jon@fourwinds.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).