tidyr
tidyr replaced separate() with a family that says what it does.
A side-by-side editorial comparison of performance and Apache Superset — 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.
Superset's tracked feed is a Helm chart tag stream with no notes attached.
The feed being tracked carries Apache Superset's Helm chart releases rather than Superset itself. Six chart versions landed between mid-July and 10 August, walking 0.21.x up to 0.22.5, and every entry carries only the project's boilerplate one-line description. What actually changed in any given chart bump is not disclosed in the feed.
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 feed being tracked carries Apache Superset's Helm chart releases rather than Superset itself. Six chart versions landed between mid-July and 10 August, walking 0.21.x up to 0.22.5, and every entry carries only the project's boilerplate one-line description. What actually changed in any given chart bump is not disclosed in the feed.
Chart releases are arriving roughly weekly, which points to steady packaging maintenance underneath — image bumps, template corrections, values-file changes — rather than a visible product push. Because the feed publishes no notes, the deployment layer is the only Superset surface observable here. Anyone tracking application-level work needs the core repository, not this stream.
The cadence supports exactly one confident call: more chart point releases within weeks. The entries carry no content indicating what those bumps will contain.
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 Apache Superset.
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 Apache Superset alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Apache Superset is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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. Apache Superset is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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 Apache Superset alternatives in Analytics are ranked by recent ship velocity. Browse the "Apache Superset alternatives" section above for the current picks, or visit /alternatives/superset for the full list with editorial commentary on each.