animation
Contribution-driven maintenance on a package whose last structural change was magick support.
Comparison · Analytics
broom vs tune
A side-by-side editorial comparison of broom and tune — release velocity, themes, recent moves, and the top alternatives to consider.
broom vs tune: at a glance
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.
What is tune?
tune extends tuning past the model itself to postprocessors, and adds a second parallel backend
tune runs hyperparameter search for tidymodels. Version 2.0.0 rewrote tune_grid() to make postprocessing tunable alongside preprocessing and the model, changed the .config naming scheme to match, and added mirai as a parallel backend next to future. Version 2.1.0 followed with quantile regression support and a replacement Gaussian process engine.
broom vs tune: editorial side-by-side
broom
0.0ANALYTICS
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.
tune
0.0ANALYTICS
tune extends tuning past the model itself to postprocessors, and adds a second parallel backend
◆ Current state
tune runs hyperparameter search for tidymodels. Version 2.0.0 rewrote tune_grid() to make postprocessing tunable alongside preprocessing and the model, changed the .config naming scheme to match, and added mirai as a parallel backend next to future. Version 2.1.0 followed with quantile regression support and a replacement Gaussian process engine.
◆ Where it's heading
Two migrations run through this timeline. The tunable surface keeps widening - first censored regression as a mode, then postprocessors via tailor - so that a candidate is now a preprocessor, model and postprocessor triple rather than just a model. The parallel story has moved from foreach to future and now to mirai, each step deprecating the last. Neither is finished.
◆ Prediction
Expect the foreach path to be removed outright, and the postprocessing surface to grow as tailor gains more steps; the GauPro switch will likely need follow-up as its behavior differs from the old engine.
Alternatives to broom and tune
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 broom or tune.
pins
pins keeps adding a storage backend per release while retiring its original API
tsibble
tsibble shipped one release in five and a half years - the data structure is finished
yardstick
yardstick made fairness metrics a first-class part of tidymodels evaluation
leaflet
leaflet relicensed to MIT and finished migrating off R's retired spatial stack
ggpubr
ggpubr reached 1.0.0 with p-value formatting presets for specific journals
Recent activity from broom and tune
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agobroombroom 1.0.13 relocates a test fixture to clear an r-devel warning
- 3mo agobroombroom 1.0.12 tracks renamed summary() output fields
- 3mo agotuneQuantile regression tuning; Bayesian search moves to GauPro
- 8mo agobroombroom 1.0.11 transfers maintainership to Emil Hvitfeldt
- 9mo agotuneFixes int_pctl() with future parallelism on last_fit()
- 11mo agobroombroom 1.0.10 clears an r-devel namespacing warning
- 11mo agotunePostprocessors become tunable; mirai joins future as a backend ⚡
- 11mo agotuneDevelopment snapshot re-enabling skipped tests
- 1y agobroombroom 1.0.9 requires R 4.1 and repairs epiR compatibility
- 1y agobroombroom 1.0.8 fixes cluster-robust intervals, drops orcutt tidiers
- 1y agotuneWarns on foreach parallelism; space-filling grids by default
- 2y agotuneFixes parallel tuning errors under multisession plans
Frequently asked questions
What is the difference between broom and tune?
They serve adjacent needs but don't currently overlap on shipped themes. broom and tune are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is broom better than tune?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. broom and tune are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
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.
What are the best alternatives to tune?
Top tune alternatives in Analytics are ranked by recent ship velocity. Browse the "tune alternatives" section above for the current picks, or visit /alternatives/tune for the full list with editorial commentary on each.