tidyr
tidyr replaced separate() with a family that says what it does.
A side-by-side editorial comparison of dowhy and StatsBase.jl — release velocity, themes, recent moves, and the top alternatives to consider.
DoWhy adds one estimation method a year and keeps its identification edge.
DoWhy is at v0.14, which added a doubly robust estimator and Python 3.13 support. The releases before it followed the same shape: v0.13 brought the Generalized Adjustment Criterion for identification, v0.12 added time-series effect estimation and a rank-based anomaly scorer. Between the feature releases sit patch versions handling pandas and CUDA breakage.
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.
DoWhy is at v0.14, which added a doubly robust estimator and Python 3.13 support. The releases before it followed the same shape: v0.13 brought the Generalized Adjustment Criterion for identification, v0.12 added time-series effect estimation and a rank-based anomaly scorer. Between the feature releases sit patch versions handling pandas and CUDA breakage.
Two threads run through the window. The identification side — DoWhy's differentiator against libraries that only estimate — keeps gaining criteria, from frontdoor with multiple variables through the Generalized Adjustment Criterion. The GCM side grows separately with missing-data handling, classifier selection logic and calibration work. The two halves are converging on a single API rather than staying separate entry points.
Given the pace of one estimator or criterion per release and the experimental flags still on missing-data support in GCM, the next release most likely promotes existing experimental features rather than opening a new estimation family.
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 dowhy or StatsBase.jl.
tidyr replaced separate() with a family that says what it does.
modeltime built conformal intervals in, then went quiet on features.
performance keeps adding ways to check a model you have already fitted.
CmdStanPy is clearing deprecations ahead of a 2.0 it keeps announcing.
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 dowhy 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. dowhy 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. dowhy 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 dowhy alternatives in Analytics are ranked by recent ship velocity. Browse the "dowhy alternatives" section above for the current picks, or visit /alternatives/dowhy 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.