Re:But no, 80-column terminals in 2020 isn't “reasonable” an...
by _ZeD_ on Saturday May 30, 2020 @01:03AM
(#23358627)
How can you make a linter for this?
[ Parent
| on HN ]
Re:But no, 80-column terminals in 2020 isn't “reasonable” an...
by erik_seaberg on Saturday May 30, 2020 @01:42AM
(#23358784)
If the author thinks it's okay, and the reviewer thinks it's okay, a robot that can't actually understand code doesn't need a vote.
Re:But no, 80-column terminals in 2020 isn't “reasonable” an...
by SenHeng on Saturday May 30, 2020 @03:18PM
(#23363825)
The reason for the robot is to have an impartial judge where neither author nor reviewer are okay with the opposing judgement. At the end of the day, a human’s judgement cycle is better reserved for something of a higher priority/use.
Re:But no, 80-column terminals in 2020 isn't “reasonable” an...
by erik_seaberg on Sunday May 31, 2020 @05:55PM
(#23373141)
Both parties should be able to cede style arguments graciously. You can't really win the argument by quoting policy, only postpone the argument and burn team goodwill.
Re:But no, 80-column terminals in 2020 isn't “reasonable” an...
by alanbernstein on Saturday May 30, 2020 @01:06AM
(#23358639)
Use warnings for long lines instead of errors?
Re:But no, 80-column terminals in 2020 isn't “reasonable” an...
by pas on Saturday May 30, 2020 @05:21AM
(#23359748)
Annotate the long line to ignore that particular linter rule. This makes it clear that it's not because the coder was lazy, ignorant, etc.
Re:But no, 80-column terminals in 2020 isn't “reasonable” an...
by zeroimpl on Saturday May 30, 2020 @11:03AM
(#23361665)
Wouldn’t that make the code less readable?
I think the point is that if 98% of your code fit under 110 chars when you weren’t using a linter, then maybe you don’t need a linter checking line length.
Re:But no, 80-column terminals in 2020 isn't “reasonable” an...
by pas on Sunday May 31, 2020 @10:02AM
(#23369651)
You can disable the max line length rule too.
I find linters helpful. Just yesterday it helped me catch a serious bug in Python. After fixing all linter warnings. The last one was a unused variable. Turns out it should have been used.
Sure, the line length is not as severe as a unused var, but that's why the important thing is to have a systematic approach to thinking about maybe-problems that the "compiler" doesn't care about.