vivekratnavel commented on pull request #921: URL: https://github.com/apache/hadoop-ozone/pull/921#issuecomment-648643111
> Your argument is that it is about text, which part of the source code does not seem to be text? why is that recommendation not applicable? None of you are willing to produce information about why your preference is better, other than it is "my preference". https://accessibility.digital.gov/visual-design/typography/ talks about recommendations on how to present text. I think this is applicable to content that is published in web pages where users do not have much flexibility to change the presentation (typeface, type size, line height etc.). The best example where this would be applicable is this website - https://hadoop.apache.org/ozone/ I find a lot of differences between source code and normal text. Even though source code is text, it is not published in a hardcoded formatting where the type size, line width and line-height recommendations by https://accessibility.digital.gov/visual-design/typography/ can be followed. Source code is not written in paragraphs with headings or sub-headings. It has varying indentations based on the language and the users have complete control over its presentation. Users can choose to read source code from Github, or choose any IDE or text editors with options to choose a typeface, line height, and line width. Now, when we enforce a hard rule on the line limit, we are excluding users who want to read 100 or 120 columns per line. > Let us take the other side, let us say that we don't move from 80 to 120, what is the loss? We lose the ability to "grep" certain texts. And we are not accommodative to those users who are not comfortable with the 80 column limit. > Are all the programmers going to be less productive? I believe this discussion is not about improving productivity. And your arguments were also to improve accessibility and be accommodative to the extent possible for others. My argument again is that we will be excluding a set of users by not extending the line limit to 120. > Let us do some research and make an informed decision; or let us leave this question open, until such time that someone who does research in this topic is kind enough to comment on this. I am not in denial of the research done by https://accessibility.digital.gov/. All I am saying is that extending the line limit to 120 characters will accommodate everybody's needs including the visually challenged. ---------------------------------------------------------------- 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: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
