ordbetareg
A brms wrapper for bounded outcomes that keeps handing users more control over the model's internals.
A side-by-side editorial comparison of ore and q2 — release velocity, themes, recent moves, and the top alternatives to consider.
A stable Oniguruma binding for R that ships correctness fixes and little else.
ore wraps the Oniguruma regex engine for R, and its recent history is entirely about making that binding safe rather than richer. The last three releases fix an infinite-loop hazard on zero-length matches, a named-group propagation bug, and locale detection at startup. The user-facing API has not moved since 1.7.1, when ore_file() began recording whether a file was read as binary.
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.
ore wraps the Oniguruma regex engine for R, and its recent history is entirely about making that binding safe rather than richer. The last three releases fix an infinite-loop hazard on zero-length matches, a named-group propagation bug, and locale detection at startup. The user-facing API has not moved since 1.7.1, when ore_file() began recording whether a file was read as binary.
This is a package in maintenance, not development. The changes cluster around C-level hygiene — memory leaks, buffer overruns, sprintf() removal, compiler warnings — which reads as keeping CRAN checks green rather than pursuing new capability. Releases arrive in pairs separated by minutes or in gaps of two years, a cadence typical of a package touched only when something breaks or a CRAN policy shifts.
The next release is most likely another correctness or toolchain fix rather than new regex functionality; the README's note about CRAN and mainline diverging suggests the two versions may be reconciled at some point, though the entries do not say when.
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 ore or q2.
A brms wrapper for bounded outcomes that keeps handing users more control over the model's internals.
One R Markdown source, four accessible formats — and a fortnight spent patching around someone else's bug.
The R package that installs Java for you stopped needing an update every time Java ships.
A young ML metrics package rewrote its own backend twice in six months chasing speed.
The AusTraits engine, generalised for anyone's trait database, now links measurements to real specimens.
The toolchain that gets R packages into the browser is optimising for payload size, not features.
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 ore alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ore alternatives" section above for the current picks, or visit /alternatives/ore 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.