← Back to home
Comparison · Infra & APIs

q2 vs rush

A side-by-side editorial comparison of q2 and rush — release velocity, themes, recent moves, and the top alternatives to consider.

q2 vs rush: at a glance

Featureq2rush
SectorInfra & APIsInfra & APIs
Velocity score6.32.5
Sparks · 30d10
Top themesrust-rewrite, publishing-toolchain, quarto, themingmlr3, distributed-computing, redis, fault-tolerance
Last editorial update10h ago4d ago
WebsiteVisit →Visit →

What is q2?

After two releases pulling ahead, q2 spends v0.23.0 back on parity: light/dark theming.

q2 is the Quarto team's Rust reimplementation of the publishing toolchain, shipping as a statically linked single binary with minisign-signed archives and a bundled Quarto Hub MCP server, still marked experimental and not production-ready. The cadence holds at roughly a release a day through mid-August, with raw commit logs standing in for curated notes. v0.22.0 was the break in the pattern — llms.txt site output and a live-share preview, the first capability the original toolchain does not have. v0.23.0 goes straight back to closing the parity gap, and does it at epic scale.

Read the full q2 trajectory →

What is rush?

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.

Read the full rush trajectory →

q2 vs rush: editorial side-by-side

Q
q2
INFRA · APIS
6.3

After two releases pulling ahead, q2 spends v0.23.0 back on parity: light/dark theming.

◆ Current state

q2 is the Quarto team's Rust reimplementation of the publishing toolchain, shipping as a statically linked single binary with minisign-signed archives and a bundled Quarto Hub MCP server, still marked experimental and not production-ready. The cadence holds at roughly a release a day through mid-August, with raw commit logs standing in for curated notes. v0.22.0 was the break in the pattern — llms.txt site output and a live-share preview, the first capability the original toolchain does not have. v0.23.0 goes straight back to closing the parity gap, and does it at epic scale.

◆ Where it's heading

The light-dark epic is the shape of how this team retires a Quarto 1 feature: a design doc, then ThemeConfig growing a parsed dark variant, dual theme compilation with color-scheme emission, attributed stylesheet links, a color-mode toggle runtime, an accessibility-aware highlight-style reader, a brand light/dark seam, and an end-to-end verification pass against quarto-web before the docs land. One phase (D) was deferred with its options recorded rather than dropped. Around it, panel-tabset support lands, format.html.css is finally copied and rebased per page, and the llms companion output gains a link-format attribute so authors control where companion links point — the one thread tying this release back to the v0.22.0 work.

◆ Prediction

Expect the remaining Q1 parity items to keep setting the release agenda, with the deferred light-dark phase D and the freshly opened panel-tabset plan the two named strands most likely to fill the next few tags. npx distribution for the standalone Quarto Hub MCP bundle is still the only distribution item the notes explicitly call planned.

R
rush
INFRA · APIS
2.5

Rush spent 2026 making distributed task ownership correct, starting with a breaking 1.0.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to q2 and rush

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 q2 or rush.

See all q2 alternatives → · See all rush alternatives →

Recent activity from q2 and rush

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoq2Light/dark themes with a color-mode toggle; panel-tabset support
  2. 4d agoq2llms.txt site output and a live-share collaborative preview
  3. 5d agoq2TOC entries carry inline markup; draft banner restored
  4. 6d agoq2Adds alias redirect stubs and diagnostic suppression
  5. 6d agoq2Bumps samod and automerge; fixes indented continuations
  6. 7d agoq2Lua filters supported; mermaid bundled instead of CDN-loaded
  7. 25d agorushWorkers start in their own mirai call so they can create local daemons
  8. 1mo agorushTask lifecycle moves onto the worker; worker ids can no longer collide
  9. 3mo agorushPhantom failed tasks and missed results fixed
  10. 4mo agorushSmaller Redis payloads and vector-valued task parameters
  11. 5mo agorushRush 1.0 rewrites the task lifecycle and drops the seed mechanism
  12. 9mo agorushwait_for_workers() can target a count or specific ids

Frequently asked questions

What is the difference between q2 and rush?

They serve adjacent needs but don't currently overlap on shipped themes. q2 is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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.

Is q2 better than rush?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. q2 is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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.

What are the best alternatives to q2?

Top q2 alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "q2 alternatives" section above for the current picks, or visit /alternatives/q2 for the full list with editorial commentary on each.

What are the best alternatives to rush?

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.