tidytext
Finished, widely taught, and shipping roxygen fixes.
A side-by-side editorial comparison of animation and workflowsets — release velocity, themes, recent moves, and the top alternatives to consider.
Contribution-driven maintenance on a package whose last structural change was magick support.
animation renders statistical and mathematical animations from R to GIF, HTML, video and LaTeX. The most recent release adds a single contributed demo; the substantive work — magick-based conversion and resolution control — landed in the 2.6/2.7 pair. Several entries carry near-identical import timestamps, so the visible dates compress the real release history.
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.
animation renders statistical and mathematical animations from R to GIF, HTML, video and LaTeX. The most recent release adds a single contributed demo; the substantive work — magick-based conversion and resolution control — landed in the 2.6/2.7 pair. Several entries carry near-identical import timestamps, so the visible dates compress the real release history.
The package has settled into contribution-driven maintenance: outside users file demos and device fixes, and the maintainer merges them. The direction set in 2.6 — dropping the shell-out to an external ImageMagick install in favour of the magick R package — was the last structural change. Nothing in the entries suggests a redesign is underway.
Expect the next release to be another accepted contribution — a demo or a device-specific fix — rather than a change to how animations are produced.
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 animation 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 animation alternatives → · See all workflowsets alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. animation 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. animation 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 animation alternatives in Analytics are ranked by recent ship velocity. Browse the "animation alternatives" section above for the current picks, or visit /alternatives/animation 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.