To be honest, the worst regular example I encounter, in either direction, is Markdown source with no hard line breaks. Markdown fully supports them, and trying to read paragraphs in whatever-hundred character lines is a painful exercise. Such irony, since part of the beauty of Markdown is dual readability in both source and rendered forms.
Excessive line breaks are bad
11–16 of 16 posts
Re: Excessive line breaks are bad
#12I’m impressed to see this from Linus. We’ve had terminals wider than 80 chars for awhile - a limit I think needs to be revisited.
Re: Excessive line breaks are bad
#13Re: Excessive line breaks are bad
#14Re: Excessive line breaks are bad
#15This is my main justification for ignoring any particular limit on line length when writing code, especially when I'm using libraries that have really long method names.
Re: Excessive line breaks are bad
#16I'm confused. This page [1] claims to be the "Linux kernel coding style" and it says "The limit on the length of lines is 80 columns and this is a strongly preferred limit". So he's reversing that without actually updating the guide? And without setting a new limit? He implies maybe "100" is a good limit but maybe "142" is even better? Weird. I know he's primarily talking about terminal output not code, but he implie…
For new code 80 columns is still the recommendation, unless this discussion causes that to be changed.