pins
pins keeps adding a storage backend per release while retiring its original API
A side-by-side editorial comparison of butcher and sparklyr — 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.
sparklyr now spends its releases absorbing dbplyr changes and feeding pysparklyr
sparklyr connects R to Spark, and almost nothing in this window originates inside the package. Releases restore compatibility after dbplyr changes its SQL generation, adapt to Spark 4.0 and to R 4.4's version-comparison changes, and convert functions into S3 methods so pysparklyr can supply its own implementations.
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.
sparklyr connects R to Spark, and almost nothing in this window originates inside the package. Releases restore compatibility after dbplyr changes its SQL generation, adapt to Spark 4.0 and to R 4.4's version-comparison changes, and convert functions into S3 methods so pysparklyr can supply its own implementations.
Two dependencies set the agenda. dbplyr repeatedly changes identifier quoting and lazy-table internals, and each change costs sparklyr a release. Meanwhile the package is being hollowed into a backend: ml_fit(), spark_apply(), spark_write_delta() and now tune_grid_spark() exist as methods so that pysparklyr, the Databricks Connect path, can override them. Dependency removal - tibble, rappdirs, digest - runs alongside as the package slims down.
Expect the next releases to continue tracking dbplyr and Spark versions, and more functions to be converted to methods as functionality shifts toward pysparklyr; new capability arriving in sparklyr itself looks unlikely.
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 sparklyr.
pins keeps adding a storage backend per release while retiring its original API
tsibble shipped one release in five and a half years - the data structure is finished
yardstick made fairness metrics a first-class part of tidymodels evaluation
tune extends tuning past the model itself to postprocessors, and adds a second parallel backend
leaflet relicensed to MIT and finished migrating off R's retired spatial stack
ggpubr reached 1.0.0 with p-value formatting presets for specific journals
See all butcher alternatives → · See all sparklyr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — maintenance — within Analytics. butcher and sparklyr 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 sparklyr 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 sparklyr alternatives in Analytics are ranked by recent ship velocity. Browse the "sparklyr alternatives" section above for the current picks, or visit /alternatives/sparklyr for the full list with editorial commentary on each.