← Back to home
Comparison · Infra & APIs

q2 vs watcher

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

q2 vs watcher: at a glance

Featureq2watcher
SectorInfra & APIsInfra & APIs
Velocity score6.30.0
Sparks · 30d10
Top themesrust-rewrite, publishing-toolchain, quarto, developer-toolingfilesystem-events, r6, build-portability, c-bindings
Last editorial update1h ago3h ago
WebsiteVisit →Visit →

What is q2?

Ten releases in six days, methodically porting Quarto's surface into a Rust binary.

q2 is the Quarto team's Rust reimplementation of Quarto, shipping as a statically linked single binary with signed release archives and a bundled Quarto Hub MCP server. It is explicitly marked experimental and not production-ready, and it is moving fast — ten releases between 7 and 13 August. The release notes are raw commit logs rather than curated summaries, and reading them shows a consistent programme: work items are investigated, design decisions recorded, tests written red, then implemented in numbered phases, with 'Q1 parity' as the recurring benchmark against the existing Quarto.

Read the full q2 trajectory →

What is watcher?

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.

Read the full watcher trajectory →

q2 vs watcher: editorial side-by-side

Q
q2
INFRA · APIS
6.3

Ten releases in six days, methodically porting Quarto's surface into a Rust binary.

◆ Current state

q2 is the Quarto team's Rust reimplementation of Quarto, shipping as a statically linked single binary with signed release archives and a bundled Quarto Hub MCP server. It is explicitly marked experimental and not production-ready, and it is moving fast — ten releases between 7 and 13 August. The release notes are raw commit logs rather than curated summaries, and reading them shows a consistent programme: work items are investigated, design decisions recorded, tests written red, then implemented in numbered phases, with 'Q1 parity' as the recurring benchmark against the existing Quarto.

◆ Where it's heading

The project is working through the original Quarto's feature surface item by item — project profiles, environment files, shortcodes in metadata, listings, callouts, crossrefs, TOC handling, aliases — while building infrastructure the original lacks, notably a numbered diagnostic catalogue (Q-2-47, Q-14-4 and so on) with a lint that requires a documentation page for every error code. Version 0.18.0's Lua filter support is the load-bearing one, since Quarto's extension ecosystem is written in Lua. Distribution choices point at the same goal: musl-static Linux builds, minisign signatures, no glibc requirement.

◆ Prediction

Expect the parity grind to continue at this cadence, with the remaining high-value Q1 features and diagnostic coverage as the visible queue. The commit logs also show npx distribution planned for the MCP server, which is the nearest thing to a stated roadmap item in these entries.

W
watcher
INFRA · APIS
0.0

watcher is a thin filesystem-events binding whose releases are mostly build work.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

With cmake gone and the bundled library current, further releases are most likely to track libfswatch upstream rather than extend the R interface.

Alternatives to q2 and watcher

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 watcher.

See all q2 alternatives → · See all watcher alternatives →

Recent activity from q2 and watcher

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

  1. 17h agoq2TOC entries carry inline markup; draft banner restored
  2. 1d agoq2Adds alias redirect stubs and diagnostic suppression
  3. 2d agoq2Bumps samod and automerge; fixes indented continuations
  4. 2d agoq2Lua filters supported; mermaid bundled instead of CDN-loaded
  5. 3d agoq2Mermaid cell options, callout titles, email autolinks
  6. 3d agoq2Project profiles, environment files, shortcodes in metadata
  7. 1mo agowatchercmake dropped from the bundled library build
  8. 3mo agowatcherBundled libfswatch updated to 1.20.1
  9. 8mo agowatcherWindows CPU usage fix for sub-second latency
  10. 1y agowatcherSystem libfswatch found in non-standard locations
  11. 1y agowatcherMultiple paths per watcher, and older Windows builds fixed
  12. 1y agowatcherAccessor methods replace public Watcher fields

Frequently asked questions

What is the difference between q2 and watcher?

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

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

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.