>> there's nothing in git commits or the code itself that forces wrapping at 80 characters > Very clever leaving out the third component here that does force i

>> there's nothing in git commits or the code itself that forces wrapping at 80 characters > Very clever leaving out the third component here that does force it. Which component is that? The SMTP protocol? According to [1], the maximum line length allowed by SMTP is 1000 octets, which is well over any maximum hard-wrapped line length for typical source code lines. > Assuming someone hasn't banally pre hard-wrapped the text. Hardwrapped text is only a problem for displays that cannot display lines as long as the hardwrapped line length. It's not a problem for displays that can display lines longer than that. To me that indicates that if enough people are using mobiles to read code and patches, then we should consider line length limits significantly less than 80 characters. > you basically can't even check a patch out on mobile without some major hassle. Mobile email clients are not suited for reviewing patches due to the fact that they typically use variable width fonts and do not provide a way to post replies inline with quoted text. But that certainly could be fixed by connecting to a machine and attaching to a screen or tmux session to review a patch. > Nah, this reply is given to even insiders that don't want to deal with that obsolete shit. Citation please. > I can say my ten-year-old laptop "works so far", but is it good, no, not really. It's really a rather weak argument to resist even changing the tiniest things. Changes should improve on what's there, not go off on a different tangent. Github wasn't even originally designed for code review and it shows. The fact that you can't have threaded discussions (like Hacker News or reddit, not like Facebook) or Twitter) on a line of code, treating commits as something completely dissociated from the review doesn't sound like an improvement to me. > Source code can be displayed using a code viewer, nicely, it works. Looking at my python code on Github on my mobile, I find that I have to scroll from side to side to view the code which is wrapped to 79 characters or less for most lines. That's no different than viewing it in a window that does not softwrap the code. How would this be any different than viewing an email with the softwrap setting turned off? >> if I have people at home streaming video while I try to use Slack or Github, they're essentially not usable > Fix your home network Why can't those tools work when I'm getting 5 to 10 kB per second downstream? Email and IRC work perfectly fine. It's the same thing if I only have a GPRS connection on my mobile. You might call protocols other than HTTP obsolete, but they still work when you don't have that much bandwidth. > You're still pretending that it was fast even with text patches, e-mails or git. Exactly how much experience do you have on the internet at dial-up speeds? I was using dial-up from 1995 through 2005. Emails, whether they contained correspondence or patches simply did not take a noticable period of time to transfer. I'm not going to bother reading the rest of your response because you're just arguing for the sake of arguing. [1] https://tools.ietf.org/html/rfc5321#section-4.5.3.1.6 https://tools.ietf.org/html/rfc5321#section-4.5.3.1.6