tidyr
tidyr replaced separate() with a family that says what it does.
A side-by-side editorial comparison of Distributions.jl and performance — release velocity, themes, recent moves, and the top alternatives to consider.
Julia's distribution library grinds forward one distribution at a time
Distributions.jl ships small, frequent releases against a large and settled API surface. Recent work splits between correctness fixes to individual distributions (LogitNormal formulas, Semicircle quantiles, Truncated Chernoff), incremental fitting support such as sufficient statistics and MLE for Chi and Chisq, and infrastructure moves like more consistent error types and global sparsity tracing through constructors.
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.
Distributions.jl ships small, frequent releases against a large and settled API surface. Recent work splits between correctness fixes to individual distributions (LogitNormal formulas, Semicircle quantiles, Truncated Chernoff), incremental fitting support such as sufficient statistics and MLE for Chi and Chisq, and infrastructure moves like more consistent error types and global sparsity tracing through constructors.
The arc is consolidation rather than expansion: dependencies are being pruned and internals made more predictable so the package composes cleanly with the rest of the Julia numerical stack. Support for sparsity tracing and looser MvNormal type aliases both point at making the library easier to drive from automatic-differentiation and optimization code.
Expect the same cadence of per-distribution fixes and fitting-method additions, with continued work on making constructors transparent to tracing and AD tooling. Nothing in these entries signals a major version or API break.
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.
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 Distributions.jl or performance.
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 Distributions.jl alternatives → · See all performance alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Distributions.jl is currently shipping more aggressively (velocity 2.5 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. Distributions.jl is currently shipping more aggressively (velocity 2.5 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 Distributions.jl alternatives in Analytics are ranked by recent ship velocity. Browse the "Distributions.jl alternatives" section above for the current picks, or visit /alternatives/distributions-jl for the full list with editorial commentary on each.
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.