Another reason for line length being important is that, with our gigantic screens of today, there's actually room to put two editor windows side by side on a single screen, one to the right of the other. Effectively each window is back to hosting only about ~100 characters though, so when doing this setting tabstop to 2 can be useful to avoid too much overrun. With all due respect for separating out stuff that indents too deep, that's not always the best thing to do, code cleanliness wise. Helper methods get lost and break flow.
On Jul 1, 7:12 pm, Greg Reddin <[email protected]> wrote: > On Thu, Jul 1, 2010 at 10:20 AM, Tor Norbye <[email protected]> wrote: > > This is 2010; people don't > > write code on tiny terminals anymore but solid IDEs on decent screens. > > I'd just like to point out there still is a niche use case similar to > the "tiny screen" use case. It has no bearing on the tabs vs. spaces > discussion, but it seems useful to mention. > > Those of us who are visually impaired are still pretty much > constrained to tiny screens even with 30" monitors. I use my OS's zoom > feature to show only the portion of the screen I'm working with. So I > still build software with lines no longer than about 90 - 100 chars. > Since Carl brought up fixed-width fonts, etc. it's useful to mention > those are helpful too. > > We may be a very small minority and most teams probably don't include > a visually-impaired person, but it's a very important consideration > for those of us who are forced to consider it :-) > > Greg -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
