dineshchitlangia commented on pull request #921: URL: https://github.com/apache/ozone/pull/921#issuecomment-818439321
> I am not trying to stir the hornet's nest here, But I came across an excellent well-researched article(In this discussion, I had asked for this data multiple times, so I thought I should post it here since I just came across this) about this issue. It takes around an hour read it, so if you are willing to spend the time please do take a look. > [Fundamentals of Optimal Code Style](https://optimal-codestyle.github.io/) > > For people who just want to read the summary of the document in relation to this issue under discussion, > Please take a look https://optimal-codestyle.github.io/#line-length > > I am just leaving this comment here for posterity, if someone asks why ozone is not 120 chars > in code length. Thank you for sharing this piece of research article, @anuengineer . So far I was not able to remove my bias for 80 chars and thus I did not share my opinion on this. The specific section correctly provides the summary but only when you read the entire paper does it make better sense because you realize the depth of research and the fine nuances covered by the author before arriving at the conclusions. That makes you agree with the section about line length. +1 for retaining the 80 character limit. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@ozone.apache.org For additional commands, e-mail: issues-h...@ozone.apache.org
