-
Think of it this way - not that long ago companies had massive documents for coding styleguides. Just as an example, here's one from Airbnb. Think about arguments about tabs vs. spaces, indentation, the placement of braces. A horrible mess, a waste of developer time and a pain to remember to make your code conform to the conventions.
-
Stream
Stream - Scalable APIs for Chat, Feeds, Moderation, & Video. Stream helps developers build engaging apps that scale to millions with performant and flexible Chat, Feeds, Moderation, and Video APIs and SDKs powered by a global edge network and enterprise-grade infrastructure.
-
Sorry, perhaps im not quite familiar with the GitHub issues you’re chatting about, but a quick search shows the Dart team actually made a very similar argument about laptops and diffs as the first reply in a thread about the 80 character max: https://github.com/dart-lang/dart_style/issues/833
-
The problem is not working on a project with 80 or 120, it's an inability to define for a given project across all team members, leading to a never ending loop of developers submitting code at the wrong line lengths, having diffs that are not diffable, wasting reviewers time, and wasting the developers time re-formatting and re-submitting code. If you ever work on a project with a lot of devs or turnover, you'll run into this issue over and over ad naseum. It's also constant on pub.dev, where people are not clear what the line length is, so they just submit their own preference often making for impossible to diff PRs.
