tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
RBesT vs webmockr
A side-by-side editorial comparison of RBesT and webmockr — release velocity, themes, recent moves, and the top alternatives to consider.
RBesT vs webmockr: at a glance
What is RBesT?
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.
What is webmockr?
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
webmockr intercepts HTTP requests in R tests and returns stubbed responses, and since 1.0.0 it covers all three clients that matter — httr, httr2 and crul. The releases through 2025 have been about shedding dependencies: internal R6 classes unexported in 2.1.0, crul demoted from Imports to Suggests in the same release, and the mutual dependency with vcr severed in 2.2.0. The package now installs and runs without pulling in the rest of the rOpenSci HTTP stack.
RBesT vs webmockr: editorial side-by-side
RBesT
0.0ANALYTICS
RBesT is teaching its Bayesian decision rules to answer two-sided questions.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
webmockr
0.0ANALYTICS
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
◆ Current state
webmockr intercepts HTTP requests in R tests and returns stubbed responses, and since 1.0.0 it covers all three clients that matter — httr, httr2 and crul. The releases through 2025 have been about shedding dependencies: internal R6 classes unexported in 2.1.0, crul demoted from Imports to Suggests in the same release, and the mutual dependency with vcr severed in 2.2.0. The package now installs and runs without pulling in the rest of the rOpenSci HTTP stack.
◆ Where it's heading
Two arcs run in sequence. The first is coverage — multiple queued responses in 0.7.0, basic auth mocking, async through crul, then httr2 — building out what can be stubbed. The second, starting with 2.0.0, is correctness and independence: stubs are now deleted if an error occurs mid-construction rather than lingering half-built, partial matching arrives for bodies and queries, and the dependency graph is pruned release by release. The 2.2.0 split from vcr landed within a minute of crul's release taking mocking control into its own clients.
◆ Prediction
RequestPattern is documented as still exported in 2.1.0 but slated for removal, so the next major release is where that lands. Expect continued dependency pruning rather than new client support — the three clients that exist are already covered.
Alternatives to RBesT and webmockr
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 webmockr.
Tplyr
Tplyr made clinical summary tables explain where every number came from.
rlistings
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
hoardr
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
riem
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
See all RBesT alternatives → · See all webmockr alternatives →
Recent activity from RBesT and webmockr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 5mo agoRBesTTwo-sided decisions across normal, binomial and Poisson outcomes ⚡
- 1y agowebmockrvcr dependency severed
- 1y agowebmockrInternal classes unexported; crul becomes an optional dependency
- 1y agoRBesTJSON read and write for mixture objects
- 1y agowebmockrFailed stub construction cleans up; partial matching extends to bodies and queries
- 1y agoRBesTess() fixed inside apply functions
- 1y agoRBesTESS for normal mixtures in the exponential family
- 1y agoRBesTTruncated mixture priors for brms, plus faster Stan models
- 2y agowebmockrhttr2 joins httr and crul as a supported client ⚡
- 2y agoRBesTStan array syntax update and CRAN system requirements
- 3y agowebmockrQueued responses, body matching and integer status codes fixed
- 3y agowebmockrRegex URI matching fixed
Frequently asked questions
What is the difference between RBesT and webmockr?
They serve adjacent needs but don't currently overlap on shipped themes. RBesT and webmockr 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.
Is RBesT better than webmockr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. RBesT and webmockr 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.
What are the best alternatives to RBesT?
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.
What are the best alternatives to webmockr?
Top webmockr alternatives in Analytics are ranked by recent ship velocity. Browse the "webmockr alternatives" section above for the current picks, or visit /alternatives/webmockr for the full list with editorial commentary on each.