3 ms·
git hubs worst problem: FIXED WIDTH CODE READING code is read way more often than written. and on github website all you can do is read it. why the viewports d
by foolfoolz 11y ago
git hubs worst problem: FIXED WIDTH CODE READING
code is read way more often than written. and on github website all you can do is read it. why the viewports don't take up the entire screen width i will never understand.
- baddox 11y agoYeah, that's a puzzling one. I've been using a browser script for a long time now to make the code view full width.
- gknoy 11y agoI don't use it often, but I have a Javascript bookmark [0] that I use in Chrome when the 100-character width is excessively abused. Over time, I found I dislike using it enough that I now try to limit my lines to 100 characters in my editor, so that my github diff presentation is easier to read. I'm sure there's an easier way to do this. I'm pretty certain I cribbed the method of setting a style from a StackOverflow article or other thing found online, but that was three years ago so I do not recall where it was. (Sorry.) I think all I did was poke around the Chrome debugger until I found the styles I needed. 0: https://gist.github.com/gknoy/0cc03a6401103bf41daf https://gist.github.com/gknoy/0cc03a6401103bf41daf
- jjgreen 11y agoIt is long lines which damage readability, and that is the fault of the gonk who wrote the code. If anything, GH's fixed-width design encourages shorter lines and so improves readability.