Stories
Slash Boxes
Comments

SoylentNews is people

posted by Fnord666 on Saturday June 20 2020, @03:04AM   Printer-friendly
from the depends-on-whether-you-code-using-emacs-or-vim? dept.

Are 80 Characters Per Line Still Reasonable In 2020?

[...] In case of the Linux kernel, that's of course [Linus Torvalds], who has recently shaken up the community with a mailing list response declaring an overly common, often even unwritten rule of code formatting as essentially obsolete: the 80-character line limitation. Considering the notoriety of his rants and crudeness, his response, which was initiated by a line break change in the submitted patch, seems downright diplomatic this time.

[Linus]' reasoning against a continuing enforcement of 80-char line limits is primarly the fact that screens are simply big enough today to comfortably fit longer lines, even with multiple terminals (or windows) next to each other. As he puts it, the only reason to stick to the limitation is using an actual VT100, which won't serve much use in kernel development anyway.

Allowing longer lines on the other hand would encourage the use of more verbose variable names and whitespace, which in turn would actually increase readability. Of course, all to a certain extent, and [Linus] obviously doesn't call for abolishing line breaks altogether. But he has a point; does it really make sense to stick to a decades old, nowadays rather arbitrary-seeming limitation in 2020?

The article then gives an overview of the history of how 80 columns became the de facto standard width. Though mentioned briefly in passing, it all really got started with the invention of the punched card dating back to 1804 when "Joseph Marie Jacquard demonstrated a mechanism to automate loom operation". The physical size of the punch card used in the 1890 United States Census was the same as US currency at that time. The cards were then known as "Hollerith cards" after the inventor Herman Hollerith. Later, IBM came to dominate the field.

As technology progressed, punch cards eventually gave way to computer terminals such at the IBM 3270 and "glass TTYs" like the DEC VT05 and Lear Siegler ADM-3A.

Computer languages were even designed around that common size. Both FORTRAN and COBOL had fixed line layouts with certain columns reserved for such things as sequence numbers, comment indicator, continuation marker, as well as the code itself.

Human factors play a role, too. A newspaper could, for example, have lines of text as long as the page is wide. It was found to be difficult to connect visually where the next line would start when one reached the end of a physical line. Hence multiple columns of text on a page. The same often holds for magazines, too.

Back to the question at hand.

I have personally used punch cards, FORTRAN, COBOL, and all of the computer terminals listed. I generally aim for 80-columns in the code I write, but I am flexible about it. Should I find that 90-100 columns better allows me to express and comprehend the code I've written, I'll err on the side of using more columns. A quick look through some code I've written revealed one case where I used 132 columns.

What about you? Hard and fast limit of 80 columns and not a single column more? 80-90? 100? Whatever it takes? Where and how do you draw the line?


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by JoeMerchant on Saturday June 20 2020, @09:18PM (2 children)

    by JoeMerchant (3937) on Saturday June 20 2020, @09:18PM (#1010468)

    what is the advantage of longer line lengths?

    For me, it's patterns. When the code is doing a bunch of nearly redundant stuff, like hooking up properties to UI elements, or somesuch. If each line can represent one of the nearly identical steps, that table of code is much easier to read than two or three lines doing each step over and over. Variations in the pattern, intentional or unintentional, show up much faster in table form.

    --
    🌻🌻 [google.com]
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 2) by JoeMerchant on Saturday June 20 2020, @09:23PM (1 child)

    by JoeMerchant (3937) on Saturday June 20 2020, @09:23PM (#1010469)

    buttonOne  .text = "one";   buttonOne  .handler =   oneHandler();  buttonOne  .visible = true;
    buttonTwo  .text = "two";   buttonTwo  .handler =   twoHandler();  buttonTwo  .visible = false;
    buttonThree.text = "three"; buttonThree.handler = threeHandler();  buttonThree.visible = true;

    as opposed to:

      buttonOne.text = "one";
      buttonOne.handler = oneHandler();
      buttonOne.visible = true;
      buttonTwo.text = "two";
      buttonTwo.handler = oneHandler();
      buttonTwo.visible = false;
      buttonThree.text = "three";
      buttonThree.visible = threeHandler();
      buttonThree.handler = true;

    --
    🌻🌻 [google.com]
    • (Score: 0) by Anonymous Coward on Saturday June 20 2020, @11:32PM

      by Anonymous Coward on Saturday June 20 2020, @11:32PM (#1010513)

      Just put a blank line in between the groups of related statements and there is no readability problem