1. 9

  2. 3

    I’m a big fan of the 80 chars, for basically all of the same reasons. It probably helps that Ruby is generally pretty terse.

    1. 3

      It also helps that 2-character tabs are pretty much the standard in Ruby.

      In OpenBSD, all C code must wrap at 80 characters with 8-space hard tabs. Makes it pretty clear when you’re writing code that is too heavily nested or verbose.

      1. 1

        Yes, that too.

        I work on a 13" MacBook Air, and I actually make my font big enough that it’s about 90 cols wide, and have vim draw a ruler at col 80.

        1. 1

          I do a similar thing with NERDtree. When it’s open, it’s 30 characters wide so the remaining editor window is 80 characters. When it’s not open, vim draws colorcolumn at 80 but is usually wrapping hard at 80 anyway.

    2. 2

      I’m a fan of 80 columns, though I’m not religious about it.

      I often code with textwidth set to 100. Monitors are big these days, and those extra 20 columns let me use some more screen space while still being able to to have two windows side-by-side.

      1. 1

        I generally agree, but I code a fair amount on my Chromebook – there’s only so much screen space, and I can only make the text so small without my eyes bleeding (not to mention that I prefer larger font sizes). There’s been a couple of cases where I’ve broken the rule on my laptop, and then started working on that code on the Chromebook and it was significantly more annoying to work on.

      2. 1

        If you have to spend a lot of time breaking lines, either your column limit is too small, or you’re using your language wrong. In other words, the optimal line length depends on the language (I appreciate the desire to standardize across languages, but I cheerfully allow ~100 char lines in C++98).

        Your editor should at least display soft-wrapped lines broken on a token boundary and wrapped in a way that respects indentation.