tidytext
Finished, widely taught, and shipping roxygen fixes.
A side-by-side editorial comparison of bbotk and mlr3learners — 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.
mlr3learners spends its releases absorbing upstream churn
mlr3learners wraps the standard model packages — ranger, xgboost, glmnet, kknn — for mlr3. Its recent history is dominated by upstream events rather than its own plans: kknn was pulled from CRAN and its learners removed in 0.11.0, then restored in 0.12.0 when the package returned. The newest release absorbs glmnet 5.0 while adding a predict_raw flag across all learners and probit support to logistic regression.
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.
mlr3learners wraps the standard model packages — ranger, xgboost, glmnet, kknn — for mlr3. Its recent history is dominated by upstream events rather than its own plans: kknn was pulled from CRAN and its learners removed in 0.11.0, then restored in 0.12.0 when the package returned. The newest release absorbs glmnet 5.0 while adding a predict_raw flag across all learners and probit support to logistic regression.
The package's job is insulation, and the changelog shows what that costs — compatibility-only releases interleaved with small capability additions that expose more of each upstream model. The direction of travel is toward giving users access to the raw upstream objects rather than hiding them.
Expect the next release to track another upstream version bump, with incremental exposure of learner-specific fields continuing alongside.
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 mlr3learners.
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 mlr3learners 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 mlr3learners alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3learners alternatives" section above for the current picks, or visit /alternatives/mlr3learners for the full list with editorial commentary on each.