November 30, 2025
Rust vs Python: comment wars
Ty
Python’s new speed cop: Rust-built Ty has fans cheering and rivals circling
TLDR: Ty is a fast Python code checker built in Rust, quietly edging toward a real release after dropping its “preview” label. The community is split: fans hype Astral’s growing power, skeptics want an official announcement, and rivals like Meta’s pyrefly stir fears of a Python tool monopoly.
Meet Ty, a super-fast tool that checks Python code for mistakes—built with Rust, the “go fast” language. The devs say you can try an online playground, or run it right now with uvx ty check. But the real show is in the comments, where the hype meets the side-eye. One user begged mods to put the bold tagline “An extremely fast Python type checker, written in Rust” front and center, while another sleuthed that Ty quietly dropped its “preview” warning nine days ago, hinting a big announcement is coming (receipt).
Then the drama hits: skeptics ask if there’s “no real news” and whether this is actually production ready, pointing to a previous thread and a fresh burial as a dupe until a real release post appears (mods said so). Meanwhile, fans of Astral’s other hits (like uv and ruff) cheer, but one commenter drops a spicy rival: Meta’s “pyrefly” might be the one thing that breaks Astral’s “total ecosystem dominance.” Cue the meme wars: “Python written in Rust is peanut butter meets chocolate,” versus “wake me when it’s official.” For normal folks: Ty promises speedy, simple checking across your project, finding packages in your virtual environment (that folder your tools use), with commands that feel push-button easy. The community? Split between ready to crown Ty and waiting for the press release.
Key Points
- •Ty is an extremely fast Python type checker written in Rust.
- •Quick start is provided via `uvx ty check`, with detailed options in the CLI reference.
- •By default, Ty checks all Python files in the current directory, subdirectories, or project starting at `pyproject.toml`.
- •Ty discovers packages via `VIRTUAL_ENV` or a `.venv` directory; otherwise specify `--python` for non-virtual environments.
- •If many errors occur when using the standard library venv, add the `venv` directory to `.gitignore` or `.ignore` and retry.