rnaturalearth
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
A side-by-side editorial comparison of bbotk and taxa — release velocity, themes, recent moves, and the top alternatives to consider.
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.
taxa started a ground-up rewrite in 2021 and has published almost nothing since.
0.4.0 began a complete rewrite aimed at making the component classes behave like base R vectors, explicitly shipping without the `taxmap` class and parking the old implementation inside metacoder until the new one matured. Four years later that is still where things stand: 0.4.2 experimented with `''` instead of `NA` for missing values and chased a vctrs test break, and 0.4.4 fixed CRAN check issues. The releases before the rewrite were the productive ones — `taxonomy_table()`, `print_tree()`, `get_dataset()`, fuzzy name matching, faster parsers.
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.
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.
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.
0.4.0 began a complete rewrite aimed at making the component classes behave like base R vectors, explicitly shipping without the `taxmap` class and parking the old implementation inside metacoder until the new one matured. Four years later that is still where things stand: 0.4.2 experimented with `''` instead of `NA` for missing values and chased a vctrs test break, and 0.4.4 fixed CRAN check issues. The releases before the rewrite were the productive ones — `taxonomy_table()`, `print_tree()`, `get_dataset()`, fuzzy name matching, faster parsers.
The rewrite has not landed. `taxmap`, the class most users came for, was never reimplemented in the new design, and the only releases since are CRAN compliance. Meanwhile metacoder still carries the old taxa, which means the ecosystem is running on the version the rewrite was meant to replace. This reads as a stalled migration rather than an active one.
Nothing in the entries indicates the rewrite is resuming; the likely next release is another CRAN-check fix. Whether `taxmap` ever arrives in the new design is unresolved.
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 taxa.
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
writexl spent nine years refusing to do formatting, then shipped all of it in 2.0.0.
rgbif is steadily pushing users off paged searching and onto real downloads.
rstanarm is community-maintained now, tracking Stan and lme4 rather than adding models.
rotl's whole release history is keeping name matching honest against a moving taxonomy.
taxize spends its releases absorbing other people's API changes, one dead source at a time.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
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.
Top taxa alternatives in Analytics are ranked by recent ship velocity. Browse the "taxa alternatives" section above for the current picks, or visit /alternatives/taxa-r for the full list with editorial commentary on each.