mlr3proba
mlr3proba is shedding weight as its survival work moves into sibling packages
A side-by-side editorial comparison of gganimate and probably — release velocity, themes, recent moves, and the top alternatives to consider.
gganimate is in caretaker mode, tracking ggplot2 and little else
gganimate animates ggplot2 graphics, and its recent releases are almost entirely about staying compatible with ggplot2 itself. The last two releases exist to adapt to ggplot2 v4; the substantive work sits back in 1.0.9, which fixed transition bugs and moved internals onto vctrs, cli and lifecycle.
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.
gganimate animates ggplot2 graphics, and its recent releases are almost entirely about staying compatible with ggplot2 itself. The last two releases exist to adapt to ggplot2 v4; the substantive work sits back in 1.0.9, which fixed transition bugs and moved internals onto vctrs, cli and lifecycle.
Development is reactive rather than directional: the package follows ggplot2's internal changes and fixes transition edge cases as they are reported. Renderer work — ragg support, dropping the png dependency for gifski — has been the only place new capability appeared, and that was several years ago.
The next release is most likely another ggplot2 compatibility pass; nothing in these entries points to new transition types or renderers.
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.
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.
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.
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 gganimate or probably.
mlr3proba is shedding weight as its survival work moves into sibling packages
mlr3viz keeps the ecosystem's plots working while the plots themselves move out
mlr3tuning is rebuilding its async machinery under a stable public surface
timetk swallowed anomalize whole, then went quiet for two years
modelbased is turning marginal effects into a full contrast grammar
easystats' parameters package absorbs one more model class every few weeks
See all gganimate alternatives → · See all probably alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. gganimate 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. gganimate 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.
Top gganimate alternatives in Analytics are ranked by recent ship velocity. Browse the "gganimate alternatives" section above for the current picks, or visit /alternatives/gganimate for the full list with editorial commentary on each.
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.