Ruff 0.16 turns 413 lint rules on by default
Astral’s Ruff 0.16 expands its default rule set from 59 rules to 413. For Python teams, that changes an update from a speed improvement into a potential cleanup campaign.
Ruff is a Rust-based Python linter and formatter. The release folds many broadly useful checks into the default configuration, making a fresh run capable of finding a much wider class of code-quality problems.
HN’s likely concern is not whether more checks are valuable. It is how a project absorbs them: defaults are convenient for greenfield code, but established repositories need an intentional migration boundary.
The default is now an opinionated code-review policy
Ruff 0.16 raises its default enabled rules from 59 to 413. Ruff’s attraction has been consolidation: a fast Rust implementation that can cover linting and formatting work Python projects previously assembled from several tools. The new default set makes that consolidation more assertive.
For a new project, the practical result is simple: run Ruff and get a broader baseline of checks without building a long configuration file. For a mature repository, the same release is a policy decision. Newly enabled diagnostics can reveal real bugs, style inconsistencies, and patterns a team accepted because previous tooling did not name them.
A better default still needs a migration plan
The HN post drew attention because the numerical jump is large, but rule count is not the point. A lint default carries an implicit promise that its warnings are worth a developer’s interruption. Teams should test the upgrade on a branch, decide whether to fix, suppress, or stage the newly reported categories, and make that boundary visible in review.
Ruff has become valuable partly by making Python tooling feel less fragmented. This release tests the other half of that promise: a unified tool also centralizes the judgment call about what code should be rejected. The useful default is the one a team can adopt deliberately, not merely the one it can enable fastest.
Get breakdowns like this every day
The top Hacker News stories, unpacked — by email, Telegram, or RSS.
This is the last story in the July 27, 2026 issue.
Go to the issue archive