tidytext
Finished, widely taught, and shipping roxygen fixes.
Comparison · Analytics
butcher vs probably
A side-by-side editorial comparison of butcher and probably — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:tidymodels
butcher vs probably: at a glance
What is butcher?
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.
What is probably?
The package that made calibration a step instead of an afterthought.
probably started as a small utility for class predictions and equivocal zones, and version 1.0.0 turned it into tidymodels' calibration and uncertainty package: cal_plot_*, cal_estimate_*, cal_validate_* and cal_apply across binary, multiclass and regression problems, plus conformal prediction intervals. Since then the work has been consolidation — a large internal refactor with no API change, split conformal and conformal quantile regression, bound_prediction(), and required_pkgs() and butcher methods so conformal objects can be deployed and stripped.
butcher vs probably: editorial side-by-side
butcher
0.0ANALYTICS
butcher expands from trimming models to trimming whole tidymodels workflows
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
probably
0.0ANALYTICS
The package that made calibration a step instead of an afterthought.
◆ Current state
probably started as a small utility for class predictions and equivocal zones, and version 1.0.0 turned it into tidymodels' calibration and uncertainty package: cal_plot_*, cal_estimate_*, cal_validate_* and cal_apply across binary, multiclass and regression problems, plus conformal prediction intervals. Since then the work has been consolidation — a large internal refactor with no API change, split conformal and conformal quantile regression, bound_prediction(), and required_pkgs() and butcher methods so conformal objects can be deployed and stripped.
◆ Where it's heading
The recent releases are about making these objects survive leaving the session. butcher and required_pkgs() methods are what a model needs to be pinned, containerised and served, and their arrival alongside workflows adding a tailor postprocessing stage and vetiver adding probably support points the same way: calibration is being moved out of analysis scripts and into the deployed pipeline. The cal_*_none() reference implementations are the tell that calibration is now something people tune rather than apply once.
◆ Prediction
Expect the calibration functions to be reachable directly from a tuned workflow's postprocessing stage rather than applied to predictions afterwards, following the tailor integration that workflows just shipped.
Alternatives to butcher and probably
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 probably.
textrecipes
Text features finally stay sparse all the way to the model.
workflowsets
workflowsets keeps widening what counts as a model worth comparing.
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 butcher alternatives → · See all probably alternatives →
Recent activity from butcher and probably
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 8mo agobutcherMethods for rset, tune_results and workflow_set; new maintainer
- 10mo agoprobablyConformal objects gain required_pkgs() and butcher methods
- 11mo agobutcherkknn methods no longer remove the call
- 1y agoprobablyggplot2 test updates and a clearer validation-set error
- 1y agoprobablyCalibration internals refactored; isotonic bootstrap bug fixed
- 1y agobutcherComponent existence check fixed; nestedmodels methods removed
- 2y agobutcherbutcher 0.3.4
- 2y agoprobablyFix grouping sensitivity to variable type
- 2y agobutcherMethods for nestedmodels and mgcv::gam; clearer butchering messages
- 3y agoprobablySplit conformal and conformal quantile regression added
- 3y agoprobablyCalibration and conformal inference arrive in tidymodels ⚡
- 3y agobutcherEight new model families gain butcher methods
Frequently asked questions
What is the difference between butcher and probably?
Both compete on the same themes — tidymodels — within Analytics. butcher and probably 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 butcher better than probably?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. butcher and probably 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 butcher?
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.
What are the best alternatives to probably?
Top probably alternatives in Analytics are ranked by recent ship velocity. Browse the "probably alternatives" section above for the current picks, or visit /alternatives/probably for the full list with editorial commentary on each.