tidytext
Finished, widely taught, and shipping roxygen fixes.
Comparison · Analytics
bbotk vs workflowsets
A side-by-side editorial comparison of bbotk and workflowsets — release velocity, themes, recent moves, and the top alternatives to consider.
bbotk vs workflowsets: at a glance
What is bbotk?
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.
What is workflowsets?
workflowsets keeps widening what counts as a model worth comparing.
workflowsets holds a grid of preprocessor and model combinations and evaluates all of them under one call to workflow_map(). The releases in view widen that grid — clustering specifications via tidyclust, censored regression via an eval_time argument, case weights — and fill in the accessors around it with collect_notes(), collect_extracts() and fit_best(). The long-running pull_*() deprecation finally reached the error stage in 1.1.1.
bbotk vs workflowsets: editorial side-by-side
bbotk
2.5ANALYTICS
bbotk is generalizing from an optimizer toolkit into an evaluation framework.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
workflowsets
0.0ANALYTICS
workflowsets keeps widening what counts as a model worth comparing.
◆ Current state
workflowsets holds a grid of preprocessor and model combinations and evaluates all of them under one call to workflow_map(). The releases in view widen that grid — clustering specifications via tidyclust, censored regression via an eval_time argument, case weights — and fill in the accessors around it with collect_notes(), collect_extracts() and fit_best(). The long-running pull_*() deprecation finally reached the error stage in 1.1.1.
◆ Where it's heading
The package's job is comparison, so its direction is set by what tidymodels can express: every time a new model paradigm lands elsewhere, workflowsets has to learn to rank it. Clustering was the largest of those steps because it has no outcome column to score against. Alongside that runs a slower cleanup — named-only optional arguments, type checking on inputs, informative errors when someone passes a workflow set to fit() — that reads as a package hardening after its API settled.
◆ Prediction
Expect the tailor postprocessors that workflows added in 1.3.0 to need representation here next, since a workflow set that cannot vary the postprocessor cannot compare calibration choices.
Alternatives to bbotk and workflowsets
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 workflowsets.
textrecipes
Text features finally stay sparse all the way to the model.
probably
The package that made calibration a step instead of an afterthought.
workflows
The tidymodels pipeline grew a third stage, and it happens after the model runs.
vetiver
Posit's MLOps package went quiet for two years, then came back to keep up with recipes.
patchwork
patchwork stopped being a ggplot composer and became a page composer.
See all bbotk alternatives → · See all workflowsets alternatives →
Recent activity from bbotk and workflowsets
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 24d agobbotkDeprecated extra argument removed from ArchiveAsync methods
- 1mo agobbotkArchiveAsync gains full push/finish/fail task API over rush
- 2mo agobbotkDominance and hypervolume computation moved to moocore
- 4mo agobbotkmlr_test_functions adds standard optimization benchmarks
- 5mo agobbotkEvalInstance base class separates evaluation from optimization ⚡
- 8mo agobbotkFix: conditions now work with OptimizerLocalSearch
- 1y agoworkflowsetscollect_extracts() added; pull_*() functions now error
- 2y agoworkflowsetsCensored regression evaluation; eval_time breaks positional args
- 3y agoworkflowsetsClustering models enter workflow sets via tidyclust ⚡
- 4y agoworkflowsetsCase weights supported across a workflow set
- 4y agoworkflowsetsUpdate models and recipes across a set; mixed inputs accepted
- 5y agoworkflowsetsextract_*() supersedes pull_*() across tidymodels
Frequently asked questions
What is the difference between bbotk and workflowsets?
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.
Is bbotk better than workflowsets?
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.
What are the best alternatives to bbotk?
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.
What are the best alternatives to workflowsets?
Top workflowsets alternatives in Analytics are ranked by recent ship velocity. Browse the "workflowsets alternatives" section above for the current picks, or visit /alternatives/workflowsets for the full list with editorial commentary on each.