Hacker News Reader

Comment by hyeongjun | Hacker News Reader

Good news. enabling 413 rules by default means most projects get useful linting without touching the config at all!

Maybe it's just me, but getting overrun with "413 x potential warnings" hardly sounds useful :) Great for greenfield, less so for existing projects. Although nowadays, fire up your agent with "/goal work through and address all lint warnings by fixing the code according to XYZ" and leave it alone for a couple of hours and I guess it's no longer an issue...

Don't get me wrong, the new level of details coming from Ruff is much appreciated and a good thing :)

> uv run ruff check --fix

Generally gets you 90% there.

In reality it got me 30% there.

That suggests it’s doing its job.

I don't think they were trying to say "No, ruff doesn't work at all", more that "gets you 90% there" might have been an over-exaggeration, or very codebase-specific number and really, YMMV.

On the 0.16.0 release it was more like 10% autofixable on the codebases I maintain. One of them had 100+ unfixable errors across less than 10k lines of code and tests in total. Previous ruff version labeled it perfectly clean on format and check with default settings.

Good thing we have LLM:s that can do the tedious work of checking each case and applying local annotations or updating the config globally! If I was stuck doing this manually, I would have just gotten rid of ruff and went back to black+pylint.

Reply on news.ycombinator.com