rnaturalearth
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
Comparison · Analytics
bbotk vs rstanarm
A side-by-side editorial comparison of bbotk and rstanarm — release velocity, themes, recent moves, and the top alternatives to consider.
bbotk vs rstanarm: at a glance
What is bbotk?
bbotk is generalizing from an optimizer toolkit into an evaluation framework.
bbotk is the black-box optimization backend behind mlr3 tuning: search spaces, terminators, archives, and an async layer built on rush. Recent releases pair steady async-API buildout with removal of the deprecated arguments that preceded it. The 1.9.0 release introduced EvalInstance as a base class for OptimInstance, separating evaluating an objective from optimizing one.
What is rstanarm?
rstanarm is community-maintained now, tracking Stan and lme4 rather than adding models.
2.32.2 is entirely infrastructure and dependency work: formula machinery migrated from lme4 to reformulas, `r_eff` no longer computed for loo by default, the Stan R packages repo replaced by R-Universe, rstantools adopted to fix build and export errors, and CRAN NOTE cleanups — contributed largely by four first-time contributors. 2.32.1 and 2.26.1 follow the same pattern, tracking rstan syntax and adding `posterior::as_draws()` support. The last release with substantive modelling content is 2.21.1, which changed how default priors are determined and flipped `autoscale` to FALSE outside default priors.
bbotk vs rstanarm: editorial side-by-side
bbotk
2.5ANALYTICS
bbotk is generalizing from an optimizer toolkit into an evaluation framework.
◆ Current state
bbotk is the black-box optimization backend behind mlr3 tuning: search spaces, terminators, archives, and an async layer built on rush. Recent releases pair steady async-API buildout with removal of the deprecated arguments that preceded it. The 1.9.0 release introduced EvalInstance as a base class for OptimInstance, separating evaluating an objective from optimizing one.
◆ Where it's heading
Two threads run through the visible history. The first is async optimization maturing: ArchiveAsync gained a full push/finish/fail vocabulary over rush tasks in 1.11.0, and 1.12.0 deleted the deprecated extra arguments it replaced. The second is dependency consolidation, with custom C hypervolume code handed to moocore and rush pinned to 1.0.0, trimming maintenance surface as the async path becomes the default.
◆ Prediction
The deprecation removals in 1.12.0 suggest the async archive API is now treated as settled; the next releases most likely build on EvalInstance rather than continuing to churn ArchiveAsync.
rstanarm
0.0ANALYTICS
rstanarm is community-maintained now, tracking Stan and lme4 rather than adding models.
◆ Current state
2.32.2 is entirely infrastructure and dependency work: formula machinery migrated from lme4 to reformulas, `r_eff` no longer computed for loo by default, the Stan R packages repo replaced by R-Universe, rstantools adopted to fix build and export errors, and CRAN NOTE cleanups — contributed largely by four first-time contributors. 2.32.1 and 2.26.1 follow the same pattern, tracking rstan syntax and adding `posterior::as_draws()` support. The last release with substantive modelling content is 2.21.1, which changed how default priors are determined and flipped `autoscale` to FALSE outside default priors.
◆ Where it's heading
The package has moved from feature development into ecosystem maintenance, and the contributor list shows why it survives: outside developers keep it compiling against a moving Stan, lme4 and CRAN. The `as_draws()` support and the reformulas migration both point the same way — rstanarm increasingly consumes shared infrastructure (posterior, reformulas, rstantools) instead of carrying its own.
◆ Prediction
Expect the next release to track another upstream change — rstan, reformulas or CRAN policy — rather than add model families. The pre-fit model surface looks settled.
Alternatives to bbotk and rstanarm
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 bbotk or rstanarm.
writexl
writexl spent nine years refusing to do formatting, then shipped all of it in 2.0.0.
rgbif
rgbif is steadily pushing users off paged searching and onto real downloads.
taxa
taxa started a ground-up rewrite in 2021 and has published almost nothing since.
rotl
rotl's whole release history is keeping name matching honest against a moving taxonomy.
taxize
taxize spends its releases absorbing other people's API changes, one dead source at a time.
See all bbotk alternatives → · See all rstanarm alternatives →
Recent activity from bbotk and rstanarm
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 24d agobbotkDeprecated extra argument removed from ArchiveAsync methods
- 1mo agobbotkArchiveAsync gains full push/finish/fail task API over rush
- 2mo agobbotkDominance and hypervolume computation moved to moocore
- 4mo agobbotkmlr_test_functions adds standard optimization benchmarks
- 5mo agobbotkEvalInstance base class separates evaluation from optimization ⚡
- 8mo agobbotkFix: conditions now work with OptimizerLocalSearch
- 10mo agorstanarmrstanarm 2.32.2 migrates formula machinery to reformulas
- 2y agorstanarmrstanarm 2.32.1 fixes unit_vector error, enables LTO
- 2y agorstanarmrstanarm 2.26.1 adopts new rstan syntax and as_draws()
- 4y agorstanarmrstanarm 2.21.3 fixes loo() and adds stan_jm offsets
- 6y agorstanarmrstanarm 2.21.1 changes default prior behaviour
Frequently asked questions
What is the difference between bbotk and rstanarm?
They serve adjacent needs but don't currently overlap on shipped themes. bbotk is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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.
Is bbotk better than rstanarm?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. bbotk is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to bbotk?
Top bbotk alternatives in Analytics are ranked by recent ship velocity. Browse the "bbotk alternatives" section above for the current picks, or visit /alternatives/bbotk for the full list with editorial commentary on each.
What are the best alternatives to rstanarm?
Top rstanarm alternatives in Analytics are ranked by recent ship velocity. Browse the "rstanarm alternatives" section above for the current picks, or visit /alternatives/rstanarm for the full list with editorial commentary on each.