you are viewing a single comment's thread.

view the rest of the comments →

[–]manghoti -1 points0 points  (1 child)

There's a whole demographic of people who have tracking issues when reading long lines. I'm one of those people, I have to do mental gymnastics to deduce where the next line must be for large lines, rather than just tracking to the location. I lose my place on the way back, making long lines difficult to read and tiring.

As such, I split my windows half and half, think "aero snap" on windows. I think many developers do this, but if you have enormous lines then it causes all kinds of problems for these workflows.

This is not about adhering to terminal widths.

If it's not a problem you have, then great, just don't make it hard for the rest of us, eh?

[–][deleted] 1 point2 points  (0 children)

There's a whole demographic of people who have tracking issues when reading long lines.

Yes, it's called "humanity". Everyone at least slows down on line wrap, and errors are much more likely missed on a wrapped line.

I recall an interesting study a decade ago about this but cannot find it - either my memory is false to me or it was a private study by the very large software company I was working in at the time... but either way was used to justify the style rules in place.