tidytext
Finished, widely taught, and shipping roxygen fixes.
A side-by-side editorial comparison of desirability2 and workflowsets — release velocity, themes, recent moves, and the top alternatives to consider.
desirability2 is making multi-metric model selection a first-class tidymodels step.
desirability2 implements desirability functions, which map several metrics onto a common 0-1 scale so they can be combined into a single objective. The package is young: three releases, the first of which only added a NEWS file. Its substance arrived in 0.1.0 with hooks into tidymodels' tune package.
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.
desirability2 implements desirability functions, which map several metrics onto a common 0-1 scale so they can be combined into a single objective. The package is young: three releases, the first of which only added a NEWS file. Its substance arrived in 0.1.0 with hooks into tidymodels' tune package.
The direction is integration rather than standalone use. Version 0.1.0 added select_best_desirability() and show_best_desirability() to resolve a tuning run against several metrics at once; 0.2.0 exported make_desirability_cols() so other packages can build on it and made data-driven limits the default, removing the need to state ranges by hand. Both releases move work from the user into the package.
The exported helper and the developer-facing desirability() API point to adoption by other tidymodels packages as the next step rather than new functionality here.
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 desirability2 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 desirability2 alternatives → · See all workflowsets alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — tidymodels — within Analytics. desirability2 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. desirability2 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 desirability2 alternatives in Analytics are ranked by recent ship velocity. Browse the "desirability2 alternatives" section above for the current picks, or visit /alternatives/desirability2 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.