rnaturalearth
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
A side-by-side editorial comparison of mlr3mbo and rredlist — release velocity, themes, recent moves, and the top alternatives to consider.
mlr3mbo picked its defaults from a benchmark study, not from taste
mlr3mbo does model-based and Bayesian optimisation for mlr3. Its 1.0.0 release added a dictionary of pre-built acquisition-function optimisers and, more consequentially, replaced the default surrogate, acquisition function and optimiser settings with values derived from a large-scale benchmark study. The releases since are corrections to the acquisition-optimiser path exposed by that new default configuration.
rredlist threw out its species-centric API in 1.0.0 and rebuilt around assessments.
rredlist 1.0.0 is a hard break: the IUCN Red List API moved to v4, and the package followed by dropping v3 support entirely, reorganising around assessments rather than species, renaming or removing most functions, changing returned data structures, and requiring users to generate a new API key. The two releases since are consolidation on that new shape — `rl_assessment_list()` and `rl_assessment_extract()` for retrieving and unpacking many assessments at once, a `scope` argument on the `*_latest()` functions, and NULL-safe extraction.
mlr3mbo does model-based and Bayesian optimisation for mlr3. Its 1.0.0 release added a dictionary of pre-built acquisition-function optimisers and, more consequentially, replaced the default surrogate, acquisition function and optimiser settings with values derived from a large-scale benchmark study. The releases since are corrections to the acquisition-optimiser path exposed by that new default configuration.
The package has moved from a toolkit that expected users to assemble a Bayesian optimisation loop into one with a defensible default loop, and the recent fixes — warm-start sizing on multi-objective archives, silently discarded terminators, stale x_domain values — are the consequences of more people running the default path.
Expect continued hardening of the acquisition-optimiser classes rather than new acquisition functions.
rredlist 1.0.0 is a hard break: the IUCN Red List API moved to v4, and the package followed by dropping v3 support entirely, reorganising around assessments rather than species, renaming or removing most functions, changing returned data structures, and requiring users to generate a new API key. The two releases since are consolidation on that new shape — `rl_assessment_list()` and `rl_assessment_extract()` for retrieving and unpacking many assessments at once, a `scope` argument on the `*_latest()` functions, and NULL-safe extraction.
Post-1.0.0 work is clearly aimed at bulk use: fetch many assessments, pull a chosen field out of each. That is a different usage pattern from the one-species-at-a-time queries the v3-era functions encouraged, and it suits the conservation-analysis workloads the package is actually used for. Deprecated v3 functions are still present and flagged for eventual removal.
The deprecated v3-era functions are the obvious next thing to disappear, and further bulk-retrieval helpers are likely given both post-1.0 releases went that way.
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 mlr3mbo or rredlist.
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.
taxa started a ground-up rewrite in 2021 and has published almost nothing since.
rotl's whole release history is keeping name matching honest against a moving taxonomy.
See all mlr3mbo alternatives → · See all rredlist alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. mlr3mbo 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. mlr3mbo 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 mlr3mbo alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3mbo alternatives" section above for the current picks, or visit /alternatives/mlr3mbo for the full list with editorial commentary on each.
Top rredlist alternatives in Analytics are ranked by recent ship velocity. Browse the "rredlist alternatives" section above for the current picks, or visit /alternatives/rredlist for the full list with editorial commentary on each.