Ruff v0.16.0 – Significant new updates – 413 default rules up from 59

Re:Ruff v0.16.0 – Significant new updates – 413 default rule... by maratc on Sunday July 26, 2026 @12:13PM (#49059572)

Yeah, I'm in the "not interested" and "don't care" camp, with the addition of "please don't come at me with your bots who would tell me what to believe and what not to believe".

If someone wants to use a linter, I have no problem with that. I don't, and I don't want others forcing one on me, especially so as most of its "results" are straight in "this doesn't matter either way" category (in my example: two spaces instead of one, replacing quotes) and the rest make my code verifiably worse (folding a list in one line).

[ Parent | on HN ]

Re:Ruff v0.16.0 – Significant new updates – 413 default rule... by colechristensen on Sunday July 26, 2026 @01:40PM (#49060395)

unwillingness to go with the flow without big arguments is what I'm talking about

[ Parent | on HN ]

Re:Ruff v0.16.0 – Significant new updates – 413 default rule... by catgary on Sunday July 26, 2026 @02:51PM (#49061141)

I think, generally speaking, the decision to enforce a linter in CI/CD pipelines is well within a project lead’s or technical director’s purview, and there seems to be a pretty broad consensus that they add value, so they’ll almost always be in CI/CD pipelines. So just use the same linter locally and format on save so you catch any issues like your comment getting folded example.

[ Parent | on HN ]