4 ms·
I agree with everything he said... except the 80 col limit. I know I'll probably lose this fight, but I frequently write code on all sorts of different screen s
by lilactown 8y ago
I agree with everything he said... except the 80 col limit. I know I'll probably lose this fight, but I frequently write code on all sorts of different screen sizes broken into split panes (Code | REPL, Code | Browser, Code - REPL | Docs) and having a line limit makes this manageable.
Maybe 80 isn't the right one, but letting code stretch out to ad-infinitum (either with awkward line breaks or having to scroll) is a big ergonomic loss for me personally.
- ajuc 8y agoI agree, and it's not mainly because of splitting the screen. Very long lines of code just read badly, even if you have the screen-space to fit them. It's easy to skip and forget where you were when you look to compare the code to something and then look back.
- dkersten 8y agoYep, there's a reason most article/blog sites use a fixed-width column of text. Long free-flowing lines of text are simply hard to read. I also used to not care about side-by-side, but now, I find it too useful. Besides, nobody wants to scroll to read git diffs.
- kjeetgill 8y agoI usually follow 80 if possible, or in Java 100, but put a hard limit at 120. There's just a need for the occasional judgement call. This seems to work well enough for two columns. Useful for editing, but indespnseble for diffs. For reference my 15" Mac has 234 columns at full screen.