Ruff

“uv and ruff took over because they were in many ways simpler and much faster than the competition”

“The formatter is part of ruff, but uv also have an undocumented "format" command, which does not produce the same results.”

“With agents it is helpful to make them run ruff and mypy to keep them honest”

“Nor go back to any of the previous alternatives Astral's products replaced.”

“Similar to black but faster, written in Rust, by the same team who created uv.”

“I see a lot less waste of tokens and reasoning retry loops of obvious errors when using Python with uv+ruff”

“I've got only 2900 errors -- which weren't errors at all just yesterday”

“find it a handy watermark for when something should be broken up into smaller, individually testable callables”

“most of the rules are nonsense and the number of rules that makes no sense is growing”

“this change will touch much, much more than that”

“stick to older ruff until team has resources to fix issues”

“You will probably have to do it all over again when these guys release even newer and shinier 0.17.0, with even more rules.”

“Compare it to some of the other options in that space and you'll see why that was a selling point.”

“the bot force worse linting decisions, and even pushes towards more bugs”

“every version introducing a bunch of new default rules which you then have to deal with immediately”

“It's also truly really fast. On an as-yet un-ruff'ed 32k SLOC python package it returns in 158ms finding 2k errors.”

“Personally I love this rule because it saves me from looking at one extra commit”

“the new rules do improve code quality. It caught quite a few things previous versions didn't.”

“I'm a big fan of the strict by default approach that Ruff and other linters have taken.”

“getting overrun with "413 x potential warnings" hardly sounds useful”

“enabling 413 rules by default means most projects get useful linting without touching the config at all”

“This is great news! With the advent of agentic coding, strong linting is more important than ever.”

“At the very least you need all the static checking machinery like Ruff, Pyright”

“obviously best practice over running AI in a pre-commit hook to do those checks and refactors”

“Python has uv, ruff and Pyrefly, and with that combination, has roughly the same agent ergonomics as Go”

“with that combination, has roughly the same agent ergonomics as Go and lower token count due to higher abstraction level”

“The ruff Python linter caught formatting and lint violations in the malicious code and blocked the CI build”

“astral built a better one, for which I am genuinely grateful to them”

“this news is good enough reason to move from Ruff back to black”

“I will start migrating from uv, ty and ruff first thing this weekend”

“wondering if I can ever work another python project after having experienced uv, ruff, and ty”

“uv and ruff's explosive growth happening alongside and despite that of LLMs demonstrates that it's not a show-stopper”

“all great tools I recently started really using and I couldn't be happier with them”

“I immediately set up up ruff, ty, pytest, pre-commit hook and GH workflow to run ruff/ty/pytest”

“Both were better in terms of user ergonomics and also much faster that what we used before”

“Stop using flake8 and use ruff instead. It's made by the same folks that make uv.”

“replacing a mountain of tools and rules with a single extremely fast linter/formatter”

“Things improved drastically over the years with Astral's ruff, uv and alpha stage ty.”

“can yell at you for having a TODO without an associated link to a ticket, which I greatly appreciate”

“I find the black/ruff formatting style in Python to be very consistent, which helps with git blame.”