5 stories
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 top HN threads: facts from the discussions, both sides, insider voices. Email, Telegram, or RSS.
Each module is parsed by the ruff parser, lowered to one shared IR, and compiled to native code by Cranelift.
A reviewer of AI-written code saw 'clear signs of vibing' and bet full CPython compatibility won't land on any reasonable timeline.
In today's GitHub Trending: sindresorhus/awesome, the curated index that spawned a thousand "awesome-*" lists; psf/black, the zero-config Python formatter; AUTOMATIC1111's Stable Diffusion web UI; and NVIDIA's Megatron-LM training library.
The page reads like a museum, not a newsstand. Two of its residents are trending as their own users drift to successors: Ruff is quietly replacing Black, and Forge and ComfyUI carry the image work AUTOMATIC1111 stopped shipping four months ago.
In last week's GitHub Trending: SimpleX (a messenger that assigns no user identifiers at all, for the privacy-maximalist crowd), CasaOS (a home-server OS that turns a spare box into a personal cloud), Plane (a self-hosted Jira and Linear alternative), and free-for-dev (a directory of free SaaS tiers).
The list sells digital independence. But its second-biggest gainer, CasaOS, hasn't merged a commit in nearly a year, and its own issue tracker is openly asking whether the project is dead.
The pitch reads like a benchmark dream: same warnings as pylint, same bugs reproduced on purpose, and black's 26.7-hour lint run finishing in 41 seconds. It was generated by Fable, an agentic coding system, with a human mostly steering.
The thread split fast. One side called it malware-SEO with an LLM-written README and asked if the project is even legit. The other side shrugged: if it passes pylint's own tests, who cares who typed it?
