2 ms·

> So this here I think is the best monitor orientation for software development. It provides the longest line lengths and no longer need to worry about that pes

> So this here I think is the best monitor orientation for software development. It provides the longest line lengths and no longer need to worry about that pesky 80 column limit. Author optimized for this metrics. If you dont need this, no need to try :D

imiric 3y ago
If the author is serious, and works in a team, they would still need to worry about that "pesky" line length limit, though. I really don't get the argument against short line lengths, and that they're somehow a relic of old display resolutions. I find them genuinely helpful. Having to glance horizontally to read code is suboptimal compared to keeping my eyes fixed on a relatively narrow block. Being able to fit more documents open side-by-side without arbitrary line breaks is always helpful, especially when merging, even on ultrawide displays. This is why I still prefer shorter lengths, and try to keep it near the traditional 80 as much as possible. I compromise when working in a team and if someone has a different preference, but I never got the appeal, honestly.
- wakeupcall 3y ago
  Agree. Shorter lines are more readable the same way narrow paragraphs in multi-column layouts are more readable, as it's easier to follow to the next line. I'm not strict on the 80 column rule. Readability for code is a balance in intent for me first and foremost, but I also do try to keep lengths close to it. I used to follow 2 source files side-by-side easily on a 16:10 monitor. I'm struggling to do that on my 16:9 now due to how long the lines are on my current codebase with a regular editor. Comparisons are hourly occurrences for me. Long lines require scrolling or word-wrapping, either of which is just horrific. If I try the same on github, which wastes even more horizontal space, two source files are barely fitting side-by-side even with 80 columns. I'm kind of surprised authors writing these long lines, which also will review those long lines in the future, and not put off by the inconvenience they're doing to themselves.

imiric 3y ago

If the author is serious, and works in a team, they would still need to worry about that "pesky" line length limit, though. I really don't get the argument against short line lengths, and that they're somehow a relic of old display resolutions. I find them genuinely helpful. Having to glance horizontally to read code is suboptimal compared to keeping my eyes fixed on a relatively narrow block. Being able to fit more documents open side-by-side without arbitrary line breaks is always helpful, especially when merging, even on ultrawide displays. This is why I still prefer shorter lengths, and try to keep it near the traditional 80 as much as possible. I compromise when working in a team and if someone has a different preference, but I never got the appeal, honestly.

wakeupcall 3y ago
Agree. Shorter lines are more readable the same way narrow paragraphs in multi-column layouts are more readable, as it's easier to follow to the next line. I'm not strict on the 80 column rule. Readability for code is a balance in intent for me first and foremost, but I also do try to keep lengths close to it. I used to follow 2 source files side-by-side easily on a 16:10 monitor. I'm struggling to do that on my 16:9 now due to how long the lines are on my current codebase with a regular editor. Comparisons are hourly occurrences for me. Long lines require scrolling or word-wrapping, either of which is just horrific. If I try the same on github, which wastes even more horizontal space, two source files are barely fitting side-by-side even with 80 columns. I'm kind of surprised authors writing these long lines, which also will review those long lines in the future, and not put off by the inconvenience they're doing to themselves.