dowhy
DoWhy adds one estimation method a year and keeps its identification edge.
A side-by-side editorial comparison of Distributions.jl and shiny — 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.
Shiny made reactive apps observable, then gave them a way to tear themselves down
Version 1.12.0 added OpenTelemetry support through the {otel} package, emitting spans for session start and end, reactive updates and individual reactive expressions, with collection depth set by an option or environment variable. The releases since have refined it - scoped collection controls in 1.12.1, cleaner stack traces in 1.13.0 - while 1.14.0 turned to lifecycle, adding session$destroy() on module proxies and a non-blocking startApp() for driving apps programmatically.
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.
Version 1.12.0 added OpenTelemetry support through the {otel} package, emitting spans for session start and end, reactive updates and individual reactive expressions, with collection depth set by an option or environment variable. The releases since have refined it - scoped collection controls in 1.12.1, cleaner stack traces in 1.13.0 - while 1.14.0 turned to lifecycle, adding session$destroy() on module proxies and a non-blocking startApp() for driving apps programmatically.
The framework is addressing the two things that make Shiny apps hard to run in production: you could not see inside the reactive graph, and you could not reliably dispose of parts of it. Tracing answers the first; scoped destruction of module session proxies answers the second. Both are aimed at long-lived, dynamically composed apps rather than at the single-file demo.
Expect the OpenTelemetry attribute names to settle once the deprecated spellings are dropped, and more of the reactive lifecycle to gain explicit teardown hooks now that session$destroy() has established the pattern. Editor integration is a likely area for follow-up after the Ark breakpoint support.
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 shiny.
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.
statsmodels ships only what the ecosystem breaks — six releases, no new statistics.
StatsBase.jl is in caretaker mode — correctness fixes in, dependency bumps out.
Iris ships steadily on a two-a-year cadence, but its feed publishes only pointers.
See all Distributions.jl alternatives → · See all shiny 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 shiny alternatives in Analytics are ranked by recent ship velocity. Browse the "shiny alternatives" section above for the current picks, or visit /alternatives/r-shiny for the full list with editorial commentary on each.