• ZOSTED@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    26
    ·
    10 months ago

    I think it’s just because they’re old. I’ve got told “ok boomer” for complaining about lines of source code longer than 80 characters.

      • ZOSTED@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        10 months ago

        Haha yeah I’ve seen the error of my ways.

        But seriously I think it varies by use case. “Tight” languages like golang, python, ruby, or most backends (other than Java)? Going over 80 is a bit of a smell. But if we’re talking about a React frontend? Then yeah, an 80 character limit is obnoxious.

        • sugar_in_your_tea@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          2
          ·
          10 months ago

          Nah, Python is a little verbose at times, so 100 is a bit better, especially for longer comprehensions with an if clause. Our team uses keyword parameters pretty much everywhere, so a lot of regular function calls wrap even at our 120-line limit (I’m trying to push us toward positional-only args to keep it under control).

        • Fushuan [he/him]@lemm.ee
          link
          fedilink
          English
          arrow-up
          1
          ·
          10 months ago

          It really depends on the use case. Scripting? 80 should suffice. Writing a complete program with classes, methods in classes, calling methods of variables, chaining method calls… 80 is very punishing. Even 130 is punishing for some pyspark methods. To apply line limits , you end up dividing calls in separate lines, which in turn makes the whole file much, much larger. Doing to it for the times it happens in 130 lines is completely fine, but with 80 a 800 lines file would be converted to 2000 at minimum. That’s not good.