desirability2
desirability2 is making multi-metric model selection a first-class tidymodels step.
A side-by-side editorial comparison of datawizard and tune — release velocity, themes, recent moves, and the top alternatives to consider.
datawizard is turning easystats' data layer into a general-purpose I/O and reshaping tool
datawizard handles the data preparation half of the easystats stack — reshaping, recoding, describing, and reading and writing files. The 1.x releases have pushed hardest on I/O: parquet via nanoparquet, then password-protected R formats, alongside a run of breaking cleanups in data_to_wide(), data_modify() and describe_distribution().
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.
datawizard handles the data preparation half of the easystats stack — reshaping, recoding, describing, and reading and writing files. The 1.x releases have pushed hardest on I/O: parquet via nanoparquet, then password-protected R formats, alongside a run of breaking cleanups in data_to_wide(), data_modify() and describe_distribution().
The package is willing to break its own interfaces to reach behavior users expect from tidyr and friends — data_to_wide() explicitly moved toward pivot_wider() semantics, and data_modify() stopped guessing whether a string was an expression. Output formatting is consolidating behind insight's display() and tinytable. The direction is fewer surprises and more file formats, not more statistics.
Expect encryption and format support to extend past R-native files if it continues, and further alignment of print and display behavior with the shared insight infrastructure.
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.
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.
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.
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 datawizard or tune.
desirability2 is making multi-metric model selection a first-class tidymodels step.
crosstalk is frozen infrastructure: four releases in five years, mostly CRAN upkeep.
cmdstanr keeps adding fast approximations beside full HMC, and fighting Windows toolchains.
comtradr's 1.0 line is a long tail of patches against a brittle UN trade API.
An htmlwidget whose release notes are mostly billboard.js version bumps, quiet since 2021.
bbotk is generalizing from an optimizer toolkit into an evaluation framework.
See all datawizard alternatives → · See all tune alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. datawizard 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. datawizard 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.
Top datawizard alternatives in Analytics are ranked by recent ship velocity. Browse the "datawizard alternatives" section above for the current picks, or visit /alternatives/datawizard for the full list with editorial commentary on each.
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.