tidyr
tidyr replaced separate() with a family that says what it does.
A side-by-side editorial comparison of performance and StatsBase.jl — 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.
StatsBase.jl is in caretaker mode — correctness fixes in, dependency bumps out.
StatsBase.jl is deep in the 0.34 patch series, releasing every few months with changes that are either small correctness fixes or bot-authored dependency bumps. The most substantive recent release, 0.34.10, fixed weighted sampling with UnitWeights, sped up unweighted ecdf, and widened quantile to accept non-Real element types. Since then the tags have thinned to CI action bumps and a diff-only note.
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.
StatsBase.jl is deep in the 0.34 patch series, releasing every few months with changes that are either small correctness fixes or bot-authored dependency bumps. The most substantive recent release, 0.34.10, fixed weighted sampling with UnitWeights, sped up unweighted ecdf, and widened quantile to accept non-Real element types. Since then the tags have thinned to CI action bumps and a diff-only note.
This is the shape of a foundational Julia package that has reached its intended scope: the API is settled, and maintenance means keeping compat bounds current and closing long-tail correctness issues raised by users. Nothing in the feed suggests new statistical capability is being staged. The most likely reason is that new work now lands in the downstream packages that build on StatsBase rather than in StatsBase itself.
Expect more 0.34.x patches on the same rhythm — CompatHelper bumps and occasional user-reported edge-case fixes — with no signal in these entries that a 0.35 or 1.0 is being prepared.
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 StatsBase.jl.
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 StatsBase.jl 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 StatsBase.jl 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 StatsBase.jl 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 StatsBase.jl alternatives in Analytics are ranked by recent ship velocity. Browse the "StatsBase.jl alternatives" section above for the current picks, or visit /alternatives/statsbase-jl for the full list with editorial commentary on each.