tidytext
Finished, widely taught, and shipping roxygen fixes.
A side-by-side editorial comparison of bbotk and hardhat — 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.
hardhat keeps adding the contracts tidymodels needs next
hardhat is the infrastructure layer under tidymodels, defining the preprocessing and extraction contracts other packages implement. Its releases read as a list of new generics and vector classes: extract_postprocessor(), extract_fit_time(), extract_tailor(), and a quantile_pred() class for quantile-regression output. The newest release is narrow warning and missing-value handling in mold().
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.
hardhat is the infrastructure layer under tidymodels, defining the preprocessing and extraction contracts other packages implement. Its releases read as a list of new generics and vector classes: extract_postprocessor(), extract_fit_time(), extract_tailor(), and a quantile_pred() class for quantile-regression output. The newest release is narrow warning and missing-value handling in mold().
Each addition here lands ahead of a user-facing feature elsewhere in tidymodels — the postprocessor and tailor generics precede the postprocessing workflow, quantile_pred() precedes quantile prediction in parsnip. The package's own surface stays deliberately small and its cadence follows what the rest of the stack is about to need.
Expect further extraction generics and prediction-type classes as tidymodels builds out postprocessing, with hardhat's own API remaining thin.
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 hardhat.
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 hardhat alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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 hardhat alternatives in Analytics are ranked by recent ship velocity. Browse the "hardhat alternatives" section above for the current picks, or visit /alternatives/hardhat for the full list with editorial commentary on each.