tidyr
tidyr replaced separate() with a family that says what it does.
A side-by-side editorial comparison of performance and Klipfolio — 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.
Dashboard analytics in slow maintenance, with admin controls the only moving part
The recent record is thin and heavily duplicated — each change appears two or three times, once with a mangled title carrying the body text. What actually shipped: a custom-role permission letting admins delegate viewer management, MFA device memory with an admin-enforced requirement, and API key access. The newest item is dated March.
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.
The recent record is thin and heavily duplicated — each change appears two or three times, once with a mangled title carrying the body text. What actually shipped: a custom-role permission letting admins delegate viewer management, MFA device memory with an admin-enforced requirement, and API key access. The newest item is dated March.
Development is concentrated on account administration rather than the analytics surface. Delegating viewer management and enforcing MFA are the concerns of a product whose growth comes from agencies and self-managed client accounts, where the buyer administers many downstream users. No dashboard, data-source or visualization work appears in the window at all.
The entries show four months without a release and no product-surface work, so there is nothing here to support a confident prediction about what ships next.
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 Klipfolio.
tidyr replaced separate() with a family that says what it does.
modeltime built conformal intervals in, then went quiet on features.
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.
See all performance alternatives → · See all Klipfolio alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. performance and Klipfolio 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 Klipfolio 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 Klipfolio alternatives in Analytics are ranked by recent ship velocity. Browse the "Klipfolio alternatives" section above for the current picks, or visit /alternatives/klipfolio for the full list with editorial commentary on each.