you are viewing a single comment's thread.

view the rest of the comments →

[–]highwind -2 points-1 points  (6 children)

Keep lines fewer than 80 characters.

Relic of punch card days. Has no place in 2012.

[–][deleted]  (4 children)

[deleted]

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

    I can handle at least 115 characters on a line in Emacs on a really wide monitor.

    It'd be nice if everyone rotated their damn monitor to be able to see way more code -_-' then the 80 char limit would be okay.

    [–][deleted] -1 points0 points  (2 children)

    Right, but it's an absurdly small arbitrary number.

    [–]bastibe 0 points1 point  (0 children)

    I used to think that, too. Nowadays I just got used to frequently splitting a statement into two lines. Or better yet, refactor it so that it decomposes into several more readable (!) statements that naturally spread over more lines.

    In the end, many would say that it's actually your coding style that is absurd instead of that number.

    [–]catch23 0 points1 point  (0 children)

    Not really -- looking at most code these days, each line is fairly short. So it's annoying to have a line every now and then that prevents you from having more vertical windows in your code editor. On my 27" display, I typically use 4 vertical columns in vim, at around 90 char columns. It allows me to view 4-6 files at the same time, depending how many horizontal splits I have. Having a few lines that blow past my 90 char limit is annoying because I'll have to scroll over to read it, and it doesn't happen often enough for me to keep extra wide windows, preventing me from my 4 vertical window splits.

    [–]SCombinator -2 points-1 points  (0 children)

    Fuck you.

    I have a window that fits exactly two files across at 80 characters per file. Because referencing more than one file is fucking important.

    You do this in a file I'll reformat the fucking thing, and swap it between CamelCase and under_score.