Hacker News Reader

Comment by lonelyOrca | Hacker News Reader

That's very helpful, thanks. Could you also perhaps comment on how the speed compares between the two? I imagine Ruff is faster, but not sure where Fixit 2 lies (order Pylint, flake8?).

Thanks again for working on this awesome project and contributing to the community!

View on HN

At the moment, it's somewhere around pylint and flake8, depending on the number of lint rules running, but that's with no caching or performance optimization beyond per-file multiprocessing. I have plans for simple caching that should generally make Fixit faster than Flake8 with a warm cache, assuming that custom lint rules are reasonably performant. Fixit already has mechanisms for tracking time spent per rule, and we plan to make it easier to see which rules are the slowest in each run.

That said, I doubt it will ever achieve performance parity with Ruff, given that it's running Python code by design. But we also believe that offering targeted lint rules with auto-fixes more than makes up for time spent running linters by reducing the number of iterations spent during development, shortening code review, etc.

Eg, if there are common mistakes in a codebase that cause frequent rejections or extra iterations in code review, custom lint rules with auto-fixes can help catch — and fix — those mistakes before developers waste hours or days waiting for avoidable rejections.

Reply on news.ycombinator.com