q2
Ten releases in six days, methodically porting Quarto's surface into a Rust binary.
A side-by-side editorial comparison of rush and watcher — release velocity, themes, recent moves, and the top alternatives to consider.
Rush spent 2026 making distributed task ownership correct, starting with a breaking 1.0.
rush is the Redis-backed distributed computing backend behind mlr3's parallel tuning: workers pull tasks, push results and are tracked through heartbeats. Since 1.0.0 in March 2026 it has shipped five releases in four months, almost all correcting how tasks and workers are owned and identified under failure. The most recent lets each worker start in its own mirai call so it can spawn local daemons.
watcher is a thin filesystem-events binding whose releases are mostly build work.
The package wraps libfswatch in an R6 Watcher class for monitoring files and directories. Seven releases over sixteen months have added a vector path argument and two accessor methods, and spent the rest of their effort on build portability — non-standard system library locations, Windows bi-arch source builds on old rtools, and most recently removing the cmake requirement so the bundled source compiles with the R toolchain alone.
rush is the Redis-backed distributed computing backend behind mlr3's parallel tuning: workers pull tasks, push results and are tracked through heartbeats. Since 1.0.0 in March 2026 it has shipped five releases in four months, almost all correcting how tasks and workers are owned and identified under failure. The most recent lets each worker start in its own mirai call so it can spawn local daemons.
The through-line is moving responsibility from the controller to the worker. 1.0.0 rewrote the task lifecycle and dropped the seed mechanism; 1.2.0 moved fail_tasks(), finish_tasks(), pop_task() and push_running_tasks() from Rush onto RushWorker so only the worker that ran a task can mark it done, and gave worker ids random suffixes so they cannot collide. 1.1.0 had already removed phantom failed tasks when a worker crashes between evaluations.
With ownership and identity settled, the remaining pressure points are heartbeat and lost-worker detection; expect the next releases to tighten failure recovery rather than add API surface.
The package wraps libfswatch in an R6 Watcher class for monitoring files and directories. Seven releases over sixteen months have added a vector path argument and two accessor methods, and spent the rest of their effort on build portability — non-standard system library locations, Windows bi-arch source builds on old rtools, and most recently removing the cmake requirement so the bundled source compiles with the R toolchain alone.
The API is deliberately small and appears finished; the work that remains is making the C dependency install cleanly everywhere. Dropping cmake follows the same move nanonext made, which is not a coincidence — both come from the same author and both are aiming at environments where installing a build system is not an option.
With cmake gone and the bundled library current, further releases are most likely to track libfswatch upstream rather than extend the R interface.
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either rush or watcher.
Ten releases in six days, methodically porting Quarto's surface into a Rust binary.
The metadata cache under pak now speaks to authenticated and corporate repositories.
R's old dependency manager now runs on a vendored copy of its own successor.
A fake web server for tests that keeps closing the gap with the real thing.
Hit 1.0, relicensed to MIT, and has shipped almost nothing but dbplyr compatibility since.
The engine under every knitted R document reached 1.0 by making evaluation behave like the console.
See all rush alternatives → · See all watcher alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. rush is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rush is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top rush alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rush alternatives" section above for the current picks, or visit /alternatives/rush for the full list with editorial commentary on each.
Top watcher alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "watcher alternatives" section above for the current picks, or visit /alternatives/watcher for the full list with editorial commentary on each.