accessr
One R Markdown source, four accessible formats — and a fortnight spent patching around someone else's bug.
Comparison · Infra & APIs
q2 vs rwasm
A side-by-side editorial comparison of q2 and rwasm — release velocity, themes, recent moves, and the top alternatives to consider.
q2 vs rwasm: at a glance
What is q2?
Two surfaces the original Quarto never had: llms.txt output and a live-share preview.
q2 is the Quarto team's Rust reimplementation, shipping as a statically linked single binary with signed archives and a bundled Quarto Hub MCP server, still marked experimental and not production-ready. The cadence has held at roughly a release a day through mid-August, with raw commit logs standing in for curated notes. Until v0.22.0 the programme read as pure parity work against the existing Quarto — investigate, record design decisions, write tests red, implement in numbered phases. That release is the first to ship capability the original toolchain does not have.
What is rwasm?
The toolchain that gets R packages into the browser is optimising for payload size, not features.
rwasm cross-compiles R packages to WebAssembly and assembles the virtual filesystem images that webR loads. Its three releases have moved from making cross-compilation work at all — Autoconf overrides, uname and pkg-config shims, OpenMP support — to controlling how the resulting artefacts are packaged and shipped. Every release is pinned to a specific webR version floor.
q2 vs rwasm: editorial side-by-side
q2
7.5INFRA · APIS
Two surfaces the original Quarto never had: llms.txt output and a live-share preview.
◆ Current state
q2 is the Quarto team's Rust reimplementation, shipping as a statically linked single binary with signed archives and a bundled Quarto Hub MCP server, still marked experimental and not production-ready. The cadence has held at roughly a release a day through mid-August, with raw commit logs standing in for curated notes. Until v0.22.0 the programme read as pure parity work against the existing Quarto — investigate, record design decisions, write tests red, implement in numbered phases. That release is the first to ship capability the original toolchain does not have.
◆ Where it's heading
The parity grind continues underneath — toc-location, add_html_dependency versioning, execute-visibility across both engines — but two strands now point past it. website.llms-txt makes a rendered site emit a machine-readable representation of itself: an llms.txt index, per-page .md companions, and a concatenated llms-full.txt, dogfooded on q2's own docs. The second is a long-running preview branch (PR #464, merged here) that turns q2 preview into a live-share editor with joinable guest sessions over an n0 relay and ephemeral, read-only-by-default boots. A reimplementation that only reaches parity has no argument for itself; these two give it one.
◆ Prediction
Expect the llms-txt and live-share strands to keep absorbing releases now that both have landed end-to-end, with the remaining Q1 parity items filling the gaps. The commit logs still name npx distribution for the standalone MCP bundle as the one explicitly planned item.
rwasm
0.0INFRA · APIS
The toolchain that gets R packages into the browser is optimising for payload size, not features.
◆ Current state
rwasm cross-compiles R packages to WebAssembly and assembles the virtual filesystem images that webR loads. Its three releases have moved from making cross-compilation work at all — Autoconf overrides, uname and pkg-config shims, OpenMP support — to controlling how the resulting artefacts are packaged and shipped. Every release is pinned to a specific webR version floor.
◆ Where it's heading
The arc runs from correctness to delivery. The first release fought the cross-compilation environment itself, isolating builds from host libraries and shimming the tools configure scripts expect. The second replaced Emscripten's own file_packager with a custom metadata path and added gzip compression for filesystem images. The third is pure coordination, rebuilding the build system for webR 0.5.0. That cadence — roughly annual, each release gated on a webR version — makes this a component of the webR release train rather than an independently moving project.
◆ Prediction
The next release will most likely follow the next webR version, since two of three releases so far have been driven by a webR floor rather than by rwasm's own agenda.
Alternatives to q2 and rwasm
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 rwasm.
rJavaEnv
The R package that installs Java for you stopped needing an update every time Java ships.
SLmetrics
A young ML metrics package rewrote its own backend twice in six months chasing speed.
traits.build
The AusTraits engine, generalised for anyone's trait database, now links measurements to real specimens.
Fail2Ban
Fail2Ban finally ships 1.1.1 after 14 months in beta, with a botched deb package on the way out the door
plogr
A logging header for Rcpp packages that sat untouched for nine years, then changed how it switches on
Recent activity from q2 and rwasm
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoq2llms.txt site output and a live-share collaborative preview ⚡
- 2d agoq2TOC entries carry inline markup; draft banner restored
- 3d agoq2Adds alias redirect stubs and diagnostic suppression
- 4d agoq2Bumps samod and automerge; fixes indented continuations
- 4d agoq2Lua filters supported; mermaid bundled instead of CDN-loaded ⚡
- 5d agoq2Mermaid cell options, callout titles, email autolinks
- 1y agorwasmBuild system realigned for webR 0.5.0
- 1y agorwasmrwasm 0.2.0 ⚡
- 2y agorwasmCross-compilation gains OpenMP, Autoconf overrides and host isolation
Frequently asked questions
What is the difference between q2 and rwasm?
They serve adjacent needs but don't currently overlap on shipped themes. q2 is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 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 rwasm?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. q2 is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 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 rwasm?
Top rwasm alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rwasm alternatives" section above for the current picks, or visit /alternatives/rwasm for the full list with editorial commentary on each.