Blaze is an experimental Rust build tool designed to make repeated builds after code edits much faster than the usual Cargo/rustc workflow. It uses familiar commands such as `blaze run`, `blaze test`, and `blaze build`; the first build runs through Cargo, while Blaze initializes in the background. Later, it keeps project compilation state in memory, recompiles only changed functions, and patches that code into the existing program rather than relinking everything. On supported projects, it can also apply changes to a running program, with the project describing save-to-running-code times of about 20 milliseconds.
The README reports average edit-build speedups over real projects of 10× on Apple silicon, 24× on Linux ARM, and 11× on Linux x86-64. On x86-64, its examples include a 20× improvement for Bun and a 19× improvement for Helix; the repository’s headline claim is that incremental builds can be up to 92× faster. These gains require trade-offs: Blaze uses several gigabytes of memory even for a small project, supports macOS on Apple silicon and Linux but not Windows, and builds with its own Rust toolchain rather than necessarily honoring a project’s pinned toolchain. The project is young, so it recommends treating Cargo checks and CI as the final validation. Its documentation covers benchmarks, compatibility, hot reload, installation, and current limitations.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.