tidyr
tidyr replaced separate() with a family that says what it does.
A side-by-side editorial comparison of performance and modeltime — release velocity, themes, recent moves, and the top alternatives to consider.
performance keeps adding ways to check a model you have already fitted.
performance is at 0.17.1, which added check_priors() for prior predictive checks on Bayesian models and gave check_overdispersion(), check_model() and check_predictions() arguments to control residual type and plot range. The releases before it are a similar mix: a -2LL criterion column in test_likelihoodratio(), Bayesian predictive checks routed through modelbased, and in 0.16.0 a set of breaking renames including RMSA to the correct RMSR.
modeltime built conformal intervals in, then went quiet on features.
modeltime is at 1.3.3, a single change making the package robust to xgboost version shifts. The feature weight sits in 1.3.2, which added a future-based parallel backend, the maape() accuracy metric and dials helpers for ADAM engine tuning, and further back in the 1.2.8 and 1.3.0 pair that introduced conformal prediction intervals and then carried them through the nested forecasting workflow.
performance is at 0.17.1, which added check_priors() for prior predictive checks on Bayesian models and gave check_overdispersion(), check_model() and check_predictions() arguments to control residual type and plot range. The releases before it are a similar mix: a -2LL criterion column in test_likelihoodratio(), Bayesian predictive checks routed through modelbased, and in 0.16.0 a set of breaking renames including RMSA to the correct RMSR.
Two consistent habits. Diagnostics keep gaining arguments to narrow what is examined — ppc_range, x_limits, maximum_dots, show_ci — which reads as a package being used on models large and awkward enough that the defaults stopped working. And simulated residuals via DHARMa keep displacing standard ones as the basis for the checks themselves.
With check_priors() newly added and Bayesian predictive checks now routed through modelbased, the next release most likely extends the Bayesian diagnostic set rather than reworking the frequentist checks.
modeltime is at 1.3.3, a single change making the package robust to xgboost version shifts. The feature weight sits in 1.3.2, which added a future-based parallel backend, the maape() accuracy metric and dials helpers for ADAM engine tuning, and further back in the 1.2.8 and 1.3.0 pair that introduced conformal prediction intervals and then carried them through the nested forecasting workflow.
The arc runs from uncertainty quantification to execution. Conformal intervals arrived first and were then threaded through nested fitting, refitting and the printed forecast tables so users can see which confidence method produced an interval. The later work moves down a layer to how forecasts are computed — a portable future backend replacing foreach tuning — rather than what they express.
With only an xgboost compatibility fix since the 1.3.2 feature release, the entries do not support a confident prediction about what comes next beyond continued dependency maintenance.
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 performance or modeltime.
tidyr replaced separate() with a family that says what it does.
CmdStanPy is clearing deprecations ahead of a 2.0 it keeps announcing.
DoWhy adds one estimation method a year and keeps its identification edge.
OpenHouse is hardening the seams where table policies and jobs quietly fail.
silx 3.0 moved its default Qt binding to PySide6 — a migration for everyone embedding it.
statsmodels ships only what the ecosystem breaks — six releases, no new statistics.
See all performance alternatives → · See all modeltime alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-language — within Analytics. performance and modeltime 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. performance and modeltime 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 performance alternatives in Analytics are ranked by recent ship velocity. Browse the "performance alternatives" section above for the current picks, or visit /alternatives/easystats-performance for the full list with editorial commentary on each.
Top modeltime alternatives in Analytics are ranked by recent ship velocity. Browse the "modeltime alternatives" section above for the current picks, or visit /alternatives/modeltime for the full list with editorial commentary on each.