One of the oldest is to keep line width 80, and many of us follow it blindly but have you ever thought why we have this practice in the first place? coding practice I believe it was to make your code more readable in the age of small monitors so that whole content can fit in the screen, or it might have originated from the age of punch card, which was used to be 80 columns wide. This sounds reasonable when we think about those old days but do you think this rule makes sense in 2019? We are now living in the age where most of the developers have got , which can show up to 180 characters, It also makes your code unnecessary long, then it actually is. large monitors doesn’t this is wastage of precious monitor space? I first come to know about line wrapping at 80, while reading Oracle Code Conventions for the , which was last revised at April 20, 1999, which under indentation says Java Programming Language 4.1 Line Length Avoid lines longer than 80 characters, since they’re not handled well by many terminals and tools. Note: Examples for use in documentation should have a shorter line length-generally no more than 70 characters. source: http://www.oracle.com/technetwork/java/javase/documentation/codeconventions-136091.html#248 If I understood correctly (I may be wrong), one goal of this rule is .I used to think that 80 was silly, but being able to go through source code written by a dozen different teams over last 7 years and not needing to re-size my window is a really nice thing. Consistent column width helps with the pace of reading code. consistency Since I mostly worked with large monitors, like with Screen Split, I also realize that we are wasting lots of precious space. The consistent column width of 80 is simply too little. LG 32MP58HQ-P 32-Inch IPS Monitor I personally use 120 unless the project I work already finalized a column width, in that case, I go for consistency. One more reason people give for still using a column with of 80 is that nowadays they are working with multiple files at once, mostly in or in their IDEs like or . VIM Eclipse IntelliJ IDEA For example, if you use standard column width you can fit a couple of files across a reason and can compare them line by line, which I believe is a real benefit. You can even do a three-way merge inspection on one screen without scrolling sideways. By the way, this should not be done at the cost of excessive wrapping. I understand that consistent columns make it easier to scan and read through text but it doesn’t matter whether it’s 80 or 120. On a closing note, I would say that consistency is nice and you must go for it but 80 or even 100 is too short. Many developers could probably live with 120 or even 150 though. Our modern widescreen high definition can easily handle more. LCD monitors It is more readable than the excessive wrapping because I personally find it much harder to read a wrapped line than just seeing the whole thing in one line. Of course, this is just preference and others will feel different. So, what do you guys think, does this rule still hold or you have already moved on? Other you may like Programming Articles The 2019 Web Developer RoadMap 10 Data Structure and Algorithms Courses to Crack Programming Interview 10 Things Java Programmer Should Learn in 2019 10 Programming languages You can Learn in 2019 10 Tools Every Java Developer Should Know 10 Reasons to Learn Java Programming languages 10 Frameworks Java and Web Developer should learn in 2019 10 Tips to become a better Java Developer in 2019 Top 5 Java Frameworks to Learn in 2019 10 Reasons to Learn Python in 2019 10 Testing Libraries Every Java Developer Should Know Thanks for reading this article so far till the end. If you like this article then please consider following me on medium ( ). if you’d like to be notified for every new post and don’t forget to follow on Twitter! javinpaul javarevisited

Oracle

Twitter

Top 10 Popular Programming Languages of All time and Their Creators

Good Programmer vs Average Programmer

Read my blog

Nominated for 2022 - HackerNoon Contributor of the Year - Django

Nominated for 2022 - HackerNoon Contributor of the Year - Online Education

Nominated for 2022 - HackerNoon Contributor of the Year - Google Cloud Platform

Nominated for 2022 - HackerNoon Contributor of the Year - Neural Networks

Too Long; Didn't Read

Make resilience your competitive advantage

Does Column Width of 80 Make Sense in 2019?

Does Column Width of 80 Make Sense in 2019?

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

10 Awesome Gift Ideas for Programmers and Geeks

A Handy Checklist of Secure Coding Practices: Protect Your App and Your Users

Understanding Chain of Responsibility Pattern in C#

Here's What Your AI-Generated Code Is Not Telling You

5 Emerging Programming Languages With a Bright Future

10 Awesome Gift Ideas for Programmers and Geeks

A Handy Checklist of Secure Coding Practices: Protect Your App and Your Users

Understanding Chain of Responsibility Pattern in C#

Here's What Your AI-Generated Code Is Not Telling You

5 Emerging Programming Languages With a Bright Future

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps