r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of RBesT and USAboundaries — release velocity, themes, recent moves, and the top alternatives to consider.
RBesT is teaching its Bayesian decision rules to answer two-sided questions.
RBesT builds meta-analytic-predictive priors — the machinery for borrowing historical control data into a new trial — and evaluates the operating characteristics of decisions made with them. The stable line has spent several releases on effective sample size: ESS for normal mixtures via a new `family` argument, boundary corrections when no responses or no non-responses are observed, and stabilised ELIR computations. The 1.9-0 release candidate extends the normal, binomial and Poisson outcome functions to two-sided decisions.
Seven years dormant, then two releases dragging every census boundary from 2020 to 2024
USAboundaries supplies contemporary and historical US boundary data — states, counties, congressional districts, cities, ZIP code tabulation areas — as sf objects, with the bulk data held in a companion USAboundariesData package. After a gap running from 2018 to late 2025, two releases a month apart refreshed the contemporary census vintage from 2020 to 2024: 0.5.0 covered everything except states, and 0.5.1 finished the job.
RBesT builds meta-analytic-predictive priors — the machinery for borrowing historical control data into a new trial — and evaluates the operating characteristics of decisions made with them. The stable line has spent several releases on effective sample size: ESS for normal mixtures via a new `family` argument, boundary corrections when no responses or no non-responses are observed, and stabilised ELIR computations. The 1.9-0 release candidate extends the normal, binomial and Poisson outcome functions to two-sided decisions.
Two currents run through the changelog. One is ESS hardening — nearly every release since 1.7-4 fixes another edge case where the ELIR calculation aborted or returned something unstable, which is what happens when a quantity used to justify prior strength to regulators gets scrutinised. The other is Stan and brms integration debt: array syntax updates, a minimum Stan version bump, truncated prior generation for `mixstanvar`, deterministic EM. The RC's contributor list shows a second active maintainer, and the work is broader than any recent stable release.
The release candidate covers all three outcome families and has already absorbed a round of review comments, so the next step is most likely the 1.9-0 CRAN release itself rather than further feature work.
USAboundaries supplies contemporary and historical US boundary data — states, counties, congressional districts, cities, ZIP code tabulation areas — as sf objects, with the bulk data held in a companion USAboundariesData package. After a gap running from 2018 to late 2025, two releases a month apart refreshed the contemporary census vintage from 2020 to 2024: 0.5.0 covered everything except states, and 0.5.1 finished the job.
For a data package the release cycle is the data vintage, and the 0.3.0 split into a separate data package was designed precisely so those refreshes would not require a code release. That the 2024 update still arrived as two package versions seven years later says the mechanism is being used sparingly. Nothing in the feed shows work on the API itself since us_cities() gained an sf return type and a states argument in 2018.
The next release is most likely another vintage refresh when the census data moves again, rather than new geographies or functions. The split of 0.5.0 and 0.5.1 suggests state boundaries are handled on a separate path from the rest and may lag again.
Other Analytics 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 RBesT or USAboundaries.
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul took mocking back from webmockr and made it a property of the client itself
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all RBesT alternatives → · See all USAboundaries alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. RBesT and USAboundaries are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. RBesT and USAboundaries are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top RBesT alternatives in Analytics are ranked by recent ship velocity. Browse the "RBesT alternatives" section above for the current picks, or visit /alternatives/rbest for the full list with editorial commentary on each.
Top USAboundaries alternatives in Analytics are ranked by recent ship velocity. Browse the "USAboundaries alternatives" section above for the current picks, or visit /alternatives/usaboundaries for the full list with editorial commentary on each.