this post was submitted on 05 Jan 2024
346 points (94.4% liked)
Games
16799 readers
599 users here now
Video game news oriented community. No NanoUFO is not a bot :)
Posts.
- News oriented content (general reviews, previews or retrospectives allowed).
- Broad discussion posts (preferably not only about a specific game).
- No humor/memes etc..
- No affiliate links
- No advertising.
- No clickbait, editorialized, sensational titles. State the game in question in the title. No all caps.
- No self promotion.
- No duplicate posts, newer post will be deleted unless there is more discussion in one of the posts.
- No politics.
Comments.
- No personal attacks.
- Obey instance rules.
- No low effort comments(one or two words, emoji etc..)
- Please use spoiler tags for spoilers.
My goal is just to have a community where people can go and see what new game news is out for the day and comment on it.
Other communities:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
I mean, that's the exact response it deserves.
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.
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).
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.
120 is the limit for me. Anything longer is crazy pills.
Yeah if I have to turn on text wrapping to read the code, then something is seriously wrong.
That's our team's limit, but I still think that's too long. I think 100 is a good compromise.