I clicked through, did a search for Ruff, then looked up the Github project. Okay, but… so what? Is this another case of "I rebuilt X in Rust and hit the front page of HN"?
It seems so.
It seems so.
See example graph: https://user-images.githubusercontent.com/1309177/212613422-...
For those of us who use pylint and flake8, this is a heaven-sent tool!
Our codebase is somewhere between 200k and 300k LOC. Running the flake8 suite takes minutes. We haven't integrated ruff, but during a test run it ran in less than a second, IIRC.
So, with, say 20-30 commits per day, that's about an hour, every day. Sure, it's not like we're usually sitting there twiddling our thumbs during builds, but sometimes we actually do have to wait for a build to get ready. Just the waiting time during those rare occasions add up.
[edit]: flake8, remarkably, dropped roughly an order of magnitude in performance between version 2 and 3. So that didn't help.
Sorry for the drive by, but did you try bisecting the flake8 change that slowed it down? Unless there were thousands of commits between releases, it would only take <10 runs to bisect, an automated bisect should be under an hour with a test case that takes a few minutes. Could be an interesting thing to try?
In either case, the information wouldn't be all that useful. We run our stuff off of Debian packages (yes, we're old school), and we're not particularly interested in maintaining our own fork.
[0] https://flake8.pycqa.org/en/latest/user/python-api.html#lega...