tidytext
Finished, widely taught, and shipping roxygen fixes.
A side-by-side editorial comparison of butcher and workflowsets — release velocity, themes, recent moves, and the top alternatives to consider.
butcher expands from trimming models to trimming whole tidymodels workflows
butcher strips the parts of fitted R model objects that bloat serialized size without being needed for prediction, and it grows one method family at a time. The 0.3.x line piled up coverage for MASS, klaR, mixOmics, ipred, survival and xgboost objects; 0.4.0 changes the target from individual models to resampling and tuning containers, and hands maintenance to Max Kuhn.
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.
butcher strips the parts of fitted R model objects that bloat serialized size without being needed for prediction, and it grows one method family at a time. The 0.3.x line piled up coverage for MASS, klaR, mixOmics, ipred, survival and xgboost objects; 0.4.0 changes the target from individual models to resampling and tuning containers, and hands maintenance to Max Kuhn.
Coverage is following where tidymodels users actually accumulate size — rset, rsplit, tune_results and workflow_set objects are the things that get large in a tuning run, not single fits. The maintainer handoff points the package further into the tidymodels orbit rather than the broad model zoo it started as. Releases are otherwise small and fix-driven.
Expect further methods for tidymodels container classes and continued upkeep against xgboost and torch-backed engines; the entries show no move toward automatic size reporting or a different API.
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.
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.
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.
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 butcher or workflowsets.
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.
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.
patchwork stopped being a ggplot composer and became a page composer.
See all butcher alternatives → · See all workflowsets alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — tidymodels — within Analytics. butcher and workflowsets 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. butcher and workflowsets 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.
Top butcher alternatives in Analytics are ranked by recent ship velocity. Browse the "butcher alternatives" section above for the current picks, or visit /alternatives/butcher for the full list with editorial commentary on each.
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.