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).
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.
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.
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).