kwb.pkgbuild
kwb.pkgbuild's CI templates went four years without a refresh, then had to be rebuilt for current runners
A side-by-side editorial comparison of q2 and rextendr — release velocity, themes, recent moves, and the top alternatives to consider.
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.
rextendr put Rust-backed R packages in the browser, then tore itself down for a 1.0.0 rebuild
rextendr is the R-side toolchain for extendr, scaffolding and compiling R packages with Rust internals. The package is mid-teardown: the 0.4-final tag in October 2025 warns that main may not work as expected and directs users to install from that tag, and April 2026's release is titled as one more developer release before 1.0.0. Meanwhile the CRAN-facing 0.4.x line did the substantive work.
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.
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.
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.
rextendr is the R-side toolchain for extendr, scaffolding and compiling R packages with Rust internals. The package is mid-teardown: the 0.4-final tag in October 2025 warns that main may not work as expected and directs users to install from that tag, and April 2026's release is titled as one more developer release before 1.0.0. Meanwhile the CRAN-facing 0.4.x line did the substantive work.
Two threads run in parallel. The first is reach: 0.4.0 added WebR support out of the box for all extendr packages by enabling the wasm32-unknown-emscripten target, and 0.4.2 followed with the panic and link-time-optimization settings needed to make those builds actually work. The second is CRAN compliance — use_cran_defaults(), vendor_pkgs(), automatic SystemRequirements fields, and configure scripts, all aimed at getting Rust-powered packages accepted on CRAN. The rebuild announced in 0.4-final is a third thread whose shape the entries do not reveal.
The stated destination is 1.0.0 built on the new Makevars-linked build process, so that release is the next milestone. What the revamp changes for existing extendr packages is not described in any entry here.
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 rextendr.
kwb.pkgbuild's CI templates went four years without a refresh, then had to be rebuilt for current runners
saperlipopette turned Git disasters into practice exercises, then passed peer review
rdocdump grew from a CRAN doc dumper into a resolver that pulls packages from anywhere
nominatimlite's real work was self-hosting and caching; 0.6.0 is an internal refactor with no API change
osrm.backend stopped trusting upstream binaries and started shipping its own
taxifydb found that its coverage audit was checking a hand-maintained list, not reality.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
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.
Top rextendr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rextendr alternatives" section above for the current picks, or visit /alternatives/rextendr for the full list with editorial commentary on each.