* Split panes in editors. With 80 chars, you can usually have two panes on screen along with a file tree, on most laptop screens. This is pretty nice to have.
* Code reviews in a web interface like Github/Gitlab - 80 chars means usually there's no need to pan, even when your browser window isn't full screen
It will definitely make people use weird variable names instead of meaningful ones.
is_included = true
could turn into, inc = true #included or increment?
That's a far worse side effect than other points raised in this thread.Was it inc? incl? incld? includ? in? incldd?
Now you have to break flow to go check. There's many ways it could be written and a chance for bugs to be introduced if you accidentally pick the wrong style. And when you read it, does the inc mean incorporated? included? includes? including? incapable? incestual?
* Too long lines are hard to read. For text 11 words per line are recommended, otherwise your eyes will loose track. 11 Words is roughly 60 characters, but code is indented so you need a bit more.
* Some people look at your code in an 80-column terminal, if you use more, this would be rude.
* Some people use a GUI diff tool that displays the code side by side, so that's already 160 characters.
- Unless that's your team's preference, you're not helping anyone.
- Same as above.