← Back to home
Comparison · Analytics

bbotk vs broom

A side-by-side editorial comparison of bbotk and broom — release velocity, themes, recent moves, and the top alternatives to consider.

bbotk vs broom: at a glance

Featurebbotkbroom
SectorAnalyticsAnalytics
Velocity score2.50.0
Sparks · 30d00
Top themesblack-box optimization, mlr3, async execution, api deprecationr, tidy-models, statistics, cran-compliance
Last editorial update54m ago3h ago
WebsiteVisit →Visit →

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.

Read the full bbotk trajectory →

What is broom?

broom's release calendar is now set by CRAN checks, not by new tidiers.

broom converts model objects from across R's statistical ecosystem into tidy data frames. Four of its last six releases exist purely to resolve R CMD check warnings and errors on r-devel or to absorb upstream package changes. Maintainership passed to Emil Hvitfeldt at 1.0.11.

Read the full broom trajectory →

bbotk vs broom: editorial side-by-side

B
bbotk
ANALYTICS
2.5

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.

B
broom
ANALYTICS
0.0

broom's release calendar is now set by CRAN checks, not by new tidiers.

◆ Current state

broom converts model objects from across R's statistical ecosystem into tidy data frames. Four of its last six releases exist purely to resolve R CMD check warnings and errors on r-devel or to absorb upstream package changes. Maintainership passed to Emil Hvitfeldt at 1.0.11.

◆ Where it's heading

Carrying hundreds of tidier methods for model classes it does not own, broom's workload is dominated by other projects' breaking changes and CRAN's evolving checks. New tidier coverage has largely migrated to the packages that define the models, leaving broom as a compatibility surface.

◆ Prediction

Expect the cadence to stay reactive, with releases triggered by r-devel check failures and upstream API shifts rather than expanded model coverage.

Alternatives to bbotk and broom

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 broom.

See all bbotk alternatives → · See all broom alternatives →

Recent activity from bbotk and broom

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 24d agobbotkDeprecated extra argument removed from ArchiveAsync methods
  2. 1mo agobbotkArchiveAsync gains full push/finish/fail task API over rush
  3. 2mo agobbotkDominance and hypervolume computation moved to moocore
  4. 3mo agobroombroom 1.0.13 relocates a test fixture to clear an r-devel warning
  5. 3mo agobroombroom 1.0.12 tracks renamed summary() output fields
  6. 4mo agobbotkmlr_test_functions adds standard optimization benchmarks
  7. 5mo agobbotkEvalInstance base class separates evaluation from optimization
  8. 8mo agobroombroom 1.0.11 transfers maintainership to Emil Hvitfeldt
  9. 8mo agobbotkFix: conditions now work with OptimizerLocalSearch
  10. 11mo agobroombroom 1.0.10 clears an r-devel namespacing warning
  11. 1y agobroombroom 1.0.9 requires R 4.1 and repairs epiR compatibility
  12. 1y agobroombroom 1.0.8 fixes cluster-robust intervals, drops orcutt tidiers

Frequently asked questions

What is the difference between bbotk and broom?

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 broom?

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 broom?

Top broom alternatives in Analytics are ranked by recent ship velocity. Browse the "broom alternatives" section above for the current picks, or visit /alternatives/broom for the full list with editorial commentary on each.