anuengineer commented on PR #921:
URL: https://github.com/apache/ozone/pull/921#issuecomment-1847702790

   @steveloughran  Unless you are really passionate about this topic, You might 
get anything from reading these papers.
   I find it fascinating to learn the methods about my own brain when we read 
things. Hence these intellectual meanderings. I promised I will share some of 
the reading material in a way that is easy to click and read. 
   
   These two are general studies on WHY in-spite of having large monitors, we 
as human beings have not
   moved to 462 character lengths.
   1.  [The Effect of Line Length and Passage Type on Reading Speed, 
Comprehension, and User 
Satisfaction](https://citeseerx.ist.psu.edu/document?repid=rep1&type=pdf&doi=4539b499d5b9d911901a99460dda3da7ce037041)
   2. [The Effects of Line Length on Reading Online News] 
(psychology.wichita.edu/surl/usabilitynews/72/LineLength.asp)
   3. Java Specific --[An Empirical Study Assessing Source Code Readability in 
Comprehension](https://www.researchgate.net/publication/337787440_An_Empirical_Study_Assessing_Source_Code_Readability_in_Comprehension)
 worth reading if you are interested in this topic. One critical argument that 
this paper makes is that if you can keep the number of nestings -- that is 
curly braces -- low, it is easier to understand. The 80 character and 100 
characters, if you assume a measure provides 2 tabs means 10 more nesting, or 6 
nesting more if you assume 4 tabs. This is an important consideration when 
moving to 100 characters from 80.
   4. If there is only ONE paper that you read, this is it. Most relevant to 
our discussion. https://optimal-codestyle.github.io/
   
   Once more, than you for improving the noise to signal ratio of this 
discussion; appreciate your kindness and time.


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to