rnaturalearth
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
A side-by-side editorial comparison of bbotk and mlr3viz — 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.
mlr3viz keeps the ecosystem's plots working while the plots themselves move out
mlr3viz supplies autoplot methods across mlr3 objects — learners, resample and benchmark results, tuning instances, ensemble feature-selection results. Recent releases are mostly defensive: suppressing ggplot2::fortify() warnings on ROC and PRC curves, pinning legend order so plots are deterministic across ggplot2 environments, and tracking mlr3 1.7.2. A visible piece of scope also left, with the LearnerSurvCoxPH plot moving to mlr3proba.
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.
mlr3viz supplies autoplot methods across mlr3 objects — learners, resample and benchmark results, tuning instances, ensemble feature-selection results. Recent releases are mostly defensive: suppressing ggplot2::fortify() warnings on ROC and PRC curves, pinning legend order so plots are deterministic across ggplot2 environments, and tracking mlr3 1.7.2. A visible piece of scope also left, with the LearnerSurvCoxPH plot moving to mlr3proba.
The package is being narrowed toward generic plotting infrastructure while learner-specific plots migrate to the packages that own those learners. What it does add is access rather than new charts — passing parameters through to precrec::autoplot(), better hints when the wrong autoplot type is requested, and a confidence-interval plot for mlr3inferr. Determinism across ggplot2 versions has become a recurring concern, which is what happens when a visualization package is depended on by documentation and tests.
Following the Cox proportional-hazards precedent, further learner-specific plots are likely to move to their owning packages, leaving mlr3viz with the cross-cutting result objects.
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 mlr3viz.
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 bbotk alternatives → · See all mlr3viz alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — mlr3 — within Analytics. bbotk and mlr3viz are shipping at a similar cadence (velocity 2.5 vs 2.5, 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. bbotk and mlr3viz are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). 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 mlr3viz alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3viz alternatives" section above for the current picks, or visit /alternatives/mlr3viz for the full list with editorial commentary on each.