beekeeper
A code generator that turns an OpenAPI spec into a working R client package, milestone by milestone.
A side-by-side editorial comparison of doctest and q2 — release velocity, themes, recent moves, and the top alternatives to consider.
doctest is leaving CRAN: 0.4.1 is the last release through R's default channel.
doctest lets R package authors write tests inline with documentation examples, generating .Rd content and test files from the same source. The current release is a small bugfix, removing empty lines that @testraw was producing in generated .Rd files. Feature work has been quiet, with the two most recent entries both correcting artifacts in generated output rather than adding capability.
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.
doctest lets R package authors write tests inline with documentation examples, generating .Rd content and test files from the same source. The current release is a small bugfix, removing empty lines that @testraw was producing in generated .Rd files. Feature work has been quiet, with the two most recent entries both correcting artifacts in generated output rather than adding capability.
The direction is distribution, not features. The last release states plainly that future versions will ship as GitHub releases or through r-universe.dev, so the package is stepping outside CRAN while continuing to be developed. Read with 0.4.0, which suppressed Source line output so example edits stop producing irrelevant test churn, the recent work is about generated output being stable and predictable.
The next versions should appear on GitHub and r-universe rather than CRAN, which means users on a CRAN-only install policy stay on 0.4.1 indefinitely. What the freedom from CRAN's review cycle gets spent on is not indicated in these entries.
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.
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 doctest or q2.
A code generator that turns an OpenAPI spec into a working R client package, milestone by milestone.
A canvas grid wrapper aiming at the row counts where R's HTML table widgets stop being usable.
An R binding whose releases are mostly the upstream JS graph engine arriving, plus port ergonomics.
Antrea turned on gossip encryption by default and made users read the upgrade guide first.
Post-1.0 Strimzi tracks Kafka releases and hardens its own defaults
Security patching gives way to a hard Node.js 22 floor for every self-hosted install.
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 3.8), with 2 editorial sparks in the last 30 days against 1. 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 3.8), with 2 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top doctest alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "doctest alternatives" section above for the current picks, or visit /alternatives/doctest for the full list with editorial commentary on each.
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.