Nobody announced it. There was no big banner, no migration guide, no "critical mass achieved" blog post. But somewhere in the last few years, the command-line tools many of us reach for every day quietly started getting rewritten in Rust.
Walk your own .bashrc and you'll probably see the pattern: rg instead of grep, fd instead of find, bat instead of cat. The names are shorter, the results come back faster, and the defaults are just... better.
The rewrite that stuck
The pattern really began with ripgrep. Andrew Gallant — better known on GitHub as BurntSushi — wrote it in Rust as a content-search tool that respects your .gitignore by default and runs on a fast regex engine that stays linear-time even on hostile patterns. His own benchmarks showed it beating grep and the Silver Searcher, often by a wide margin, and ripgrep put loud numbers behind the claim instead of just talking. Developers noticed, and ripgrep became the search engine powering built-in search in editors like VS Code.
Ripgrep proved the formula: take a Unix classic, rewrite it in Rust, ship a single static binary everywhere, and let raw speed plus sane defaults do the marketing.
The pattern repeated
The same idea cascaded through the toolbox. fd (by David Peter, aka sharkdp) is a fast, user-friendly alternative to find with parallelized directory traversal and gitignore-aware defaults — you type fd PATTERN instead of find -iname '*PATTERN*'. bat (same author) is cat with syntax highlighting and Git integration. zoxide, written by Ajeet D'Souza, is the "smarter cd" that remembers which directories you visit most, inspired by the older z and autojump and working across all major shells.
The through-line is worth noticing: these aren't radical new ideas. They're the same commands you already know, sharpened up — faster, safer to script, and less frustrating out of the box.
Python got an upgrade too
The most consequential entry may be on the Python side. uv, built by Astral — the company behind the Ruff linter, founded by Charlie Marsh — is a Python package, environment, and project manager written in Rust. Astral positions it as a drop-in replacement for pip, pip-tools, pipx, poetry, virtualenv, and more, with benchmarks claiming 10–100x speedups over pip, especially with a warm cache. If you've ever watched pip stall on a slow dependency tree, the difference is startling.
There's even a Rust tool to quantify all this: hyperfine (also by sharkdp) is a command-line benchmarking tool that runs commands repeatedly, handles warmup and caching effects, and exports clean CSV or Markdown comparisons. Developers use it to settle the very "is this rewrite actually faster?" argument that keeps the ecosystem honest.
A balanced view
I should be careful not to overstate it. "Every tool is now Rust" is simply false. Plenty of excellent software remains written in C, Go, or Python, and some things — glue code and quick higher-level scripting — are rarely worth rewriting at all. Rust suits one job especially well: single, fast, cross-platform CLI binaries where safety and startup time matter. That's exactly the niche it keeps winning.
So this isn't a takeover — it's a quiet consolidation. Standardize on rg for search and fd for finding, and your terminal feels faster immediately. If you touch Python, try uv once. And when you're unsure whether a rewrite is worth it, hyperfine will settle the argument.
Rust didn't seize the toolbox. It just kept building a better version of what was already there — one command at a time.