5 ms·

This is a great talk and I really like the second part where he promotes writing your own adapters for non-idiomatic third-party libraries. That being said, I

This is a great talk and I really like the second part where he promotes writing your own adapters for non-idiomatic third-party libraries. That being said, I almost couldn't get past the obnoxious rant at the beginning against maximum line length. The reasons for the rule are made very clear in pep8 as well as the fact that it's not a hard rule and it's fine to override it in your team if you all agree on longer lines.

JustSomeNobody 11y ago
I don't think it was obnoxious. But, anytime someone is going to bring up code formatting, others will get their panties all in a twist. It's what people like to argue about when they don't want to argue about real problems.
coldtea 11y ago
>The reasons for the rule are made very clear in pep8 And are still BS with today's monitors (including laptop monitors). Besides, PEP8 itself goes on to say: " For code maintained exclusively or primarily by a team that can reach agreement on this issue, it is okay to increase the nominal line length from 80 to 100 characters (effectively increasing the maximum length to 99 characters), provided that comments and docstrings are still wrapped at 72 characters."
- masklinn 11y ago
  > And are still BS with today's monitors (including laptop monitors). My 15" laptop monitor can only (readably to me) fit two 100-wide buffers in a visually barebone editor (emacs), move to an editor or IDE where the UI takes more horizontal space because of sidebars (Atom, IntelliJ) and the buffers are close to 80-wide, so 80-wide is a perfectly fine limit as far as I'm concerned. Until I have to perform a 3-way merge, then 80-wide doesn't fit anymore. And age will eventually catch up to me and make things worse.
  - coldtea 11y ago
    Missing the point that you don't have to have ALL your lines > 80. Just the few that need to be so. And for those, you can always either wrap or scroll a little to see them in a 3 way merge, it's not a big deal. Heck, in the eighties that you champion and that they got that rule, they worked with a single 80-wide terminal view, not 2 100-wide side by side and no 3 way merges.
deleted 11y ago
[deleted]
cafard 11y ago
Many years ago I worked as a copy editor. For a while I imagined, as many copy editors did, that my task was to enforce the rules of the University of Chicago's Manual of Style, especially regarding placement of punctuation with respect to quotation marks, "which" v. "that", etc. Eventually, I understood that making such changes was useful, but not really what editing should be about. It is possible to have unreadable or awkward prose with perfect comma placement, semicolon discipline, and no "which"es without a comma before them. I doubt that I was or am nearly as good an editor as he is a coder. Yet I think that there is a logical progression (not a natural progression, since we don't all make it) from knowing the rules to knowing what the rules are for, to having the confidence to break them when it makes sense.

JustSomeNobody 11y ago

I don't think it was obnoxious. But, anytime someone is going to bring up code formatting, others will get their panties all in a twist. It's what people like to argue about when they don't want to argue about real problems.

coldtea 11y ago

>The reasons for the rule are made very clear in pep8 And are still BS with today's monitors (including laptop monitors). Besides, PEP8 itself goes on to say: " For code maintained exclusively or primarily by a team that can reach agreement on this issue, it is okay to increase the nominal line length from 80 to 100 characters (effectively increasing the maximum length to 99 characters), provided that comments and docstrings are still wrapped at 72 characters."

masklinn 11y ago
> And are still BS with today's monitors (including laptop monitors). My 15" laptop monitor can only (readably to me) fit two 100-wide buffers in a visually barebone editor (emacs), move to an editor or IDE where the UI takes more horizontal space because of sidebars (Atom, IntelliJ) and the buffers are close to 80-wide, so 80-wide is a perfectly fine limit as far as I'm concerned. Until I have to perform a 3-way merge, then 80-wide doesn't fit anymore. And age will eventually catch up to me and make things worse.
- coldtea 11y ago
  Missing the point that you don't have to have ALL your lines > 80. Just the few that need to be so. And for those, you can always either wrap or scroll a little to see them in a 3 way merge, it's not a big deal. Heck, in the eighties that you champion and that they got that rule, they worked with a single 80-wide terminal view, not 2 100-wide side by side and no 3 way merges.

deleted 11y ago

[deleted]

cafard 11y ago

Many years ago I worked as a copy editor. For a while I imagined, as many copy editors did, that my task was to enforce the rules of the University of Chicago's Manual of Style, especially regarding placement of punctuation with respect to quotation marks, "which" v. "that", etc. Eventually, I understood that making such changes was useful, but not really what editing should be about. It is possible to have unreadable or awkward prose with perfect comma placement, semicolon discipline, and no "which"es without a comma before them. I doubt that I was or am nearly as good an editor as he is a coder. Yet I think that there is a logical progression (not a natural progression, since we don't all make it) from knowing the rules to knowing what the rules are for, to having the confidence to break them when it makes sense.