News for hackers. Stuff that matters.

A comment on The 80/24 Rule. Parent comment

Re:The 80/24 Rule by mumblemumble on Friday November 15, 2019 @09:29AM (#21545059)
About a year back I moved from 120 back down to 100. The rationale was that, even on a large monitor, it was difficult to fit multiple source files side-by-side at a font size I could read comfortably. On a laptop monitor, it was hopeless.

I also noticed, during code reviews, that people read and digest statements that are broken up into multiple lines much more carefully than they do compound statements that live on a single line. Leaving me to think that line width is not just an aesthetic matter. It's really a very impactful decision that can have an important, if subtle, influence on overall software quality.

[ Parent | on HN ]
Re:The 80/24 Rule by Dylan16807 on Friday November 15, 2019 @02:54PM (#21548156)
> About a year back I moved from 120 back down to 100. The rationale was that, even on a large monitor, it was difficult to fit multiple source files side-by-side at a font size I could read comfortably. On a laptop monitor, it was hopeless.

It very much depends on the screen. With a 32 inch screen you can fit three 120-column views at the equivalent of 100 DPI at default zoom. Or even better, six 120x40 views.

[ Parent | on HN ]
Re:The 80/24 Rule by giancarlostoro on Friday November 15, 2019 @11:20AM (#21546079)
Yeah that's one argument I have heard, I guess I try to go 79 and if it gets lost and I'm at 120 I am not gonna cry about it too much, but anything over 120 characters is pushing it. But yeah, some super long lines I try to bring back. I do know about the split screen thing since PEP-8 outlines some of these things for Python code and I've read a lot of articles about why PEP-8 makes sense.
[ Parent | on HN ]