tidytext
Finished, widely taught, and shipping roxygen fixes.
A side-by-side editorial comparison of bbotk and mlr3cluster — 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.
mlr3cluster went from a handful of clusterers to covering the field
mlr3cluster supplies clustering learners to the mlr3 framework. Over three releases it added roughly a dozen learners — CLARA, k-prototypes, spectral, then a batch of nine covering finite mixtures, spherical and directional families, self-organising maps, spatio-temporal DBSCAN and robust trimmed clustering. The newest release fixes predict-time behaviour across the hierarchical learners.
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.
mlr3cluster supplies clustering learners to the mlr3 framework. Over three releases it added roughly a dozen learners — CLARA, k-prototypes, spectral, then a batch of nine covering finite mixtures, spherical and directional families, self-organising maps, spatio-temporal DBSCAN and robust trimmed clustering. The newest release fixes predict-time behaviour across the hierarchical learners.
The package is at the tail end of a coverage push, and the emphasis has shifted from adding algorithms to making the ones it has behave correctly at prediction time — cutting trees at the current k, reclustering coresets, failing informatively on unsupported metric combinations. That is the normal sequence after a rapid expansion.
Expect further predict-path corrections and parameter-set alignment across the newly added learners before any more algorithms arrive.
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 mlr3cluster.
Finished, widely taught, and shipping roxygen fixes.
Text features finally stay sparse all the way to the model.
The package that made calibration a step instead of an afterthought.
workflowsets keeps widening what counts as a model worth comparing.
The tidymodels pipeline grew a third stage, and it happens after the model runs.
Posit's MLOps package went quiet for two years, then came back to keep up with recipes.
See all bbotk alternatives → · See all mlr3cluster alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — mlr3 — within Analytics. 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 mlr3cluster alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3cluster alternatives" section above for the current picks, or visit /alternatives/mlr3cluster for the full list with editorial commentary on each.