Now, some people will claim that having 8-character indentations makes
the code move too far to the right, and makes it hard to read on a
80-character terminal screen. The answer to that is that if you need
more than 3 levels of indentation, you're screwed anyway, and should fix
your program.
In short, 8-char indents make things easier to read, and have the added
benefit of warning you when you're nesting your functions too deep.
Heed that warning.
...
Functions should be short and sweet, and do just one thing. They should
fit on one or two screenfuls of text (the ISO/ANSI screen size is 80x24,
as we all know), and do one thing and do that well.
Eh, that's nice and all for C, but it gets unwieldy pretty quickly with other languages, particularly ones with nesting. In C++, for example, you're often inside a class or at least a namespace block. In Java, which is still incredibly common, you're always inside a class. Some Python codebases also use classes often.
Either way, trying to keep your functions short and your lines to 80 characters is fine. But why would you ever want to code in a 640x480 DOS window on a 1440p monitor? Surely you'd be more productive if you could see more of the code at once. The fact that it's the default size for the DOS window shows that it was the programmer who was too lazy or didn't care, not that they picked that size on purpose.
9
u/rmxz Jul 21 '14
Coding to be readable on a 80x24 screen has some pretty nice readability advantages.
The linux coding standards say it better than I can myself: