dowhy
DoWhy adds one estimation method a year and keeps its identification edge.
A side-by-side editorial comparison of dbt Core and silx — release velocity, themes, recent moves, and the top alternatives to consider.
The Rust rewrite crosses from alpha to beta, and it can now bind SQL without touching the warehouse.
dbt is running two release lines at once. The 1.x Python line reached 1.12.0 in July, a GA that removed the experimental dbt login command and the bundled dbt-state plugin outright while adding the v2 semantic layer YAML parsing. The 2.0 Fusion line — the Rust engine — moved through five alphas and reached its first beta on August 10, carrying catalog-free binding, dbt state explain, redundant-test skipping, and a lint rule system that understands node selection.
silx 3.0 moved its default Qt binding to PySide6 — a migration for everyone embedding it.
silx releases a couple of times a year and reached 3.0.0 in April 2026, which raised the Python floor to 3.10 and switched the default Qt binding to PySide6. The same release reworked the viewer's data views: 3D scatter support, dedicated RGB(A) image views, the composite ImageView split into Plot2dView and ComplexImageView, and NXdata stacks displayed as images. 3.1.0 has since added asinh axis scaling, the twilight colormaps, and dark-theme icons.
dbt is running two release lines at once. The 1.x Python line reached 1.12.0 in July, a GA that removed the experimental dbt login command and the bundled dbt-state plugin outright while adding the v2 semantic layer YAML parsing. The 2.0 Fusion line — the Rust engine — moved through five alphas and reached its first beta on August 10, carrying catalog-free binding, dbt state explain, redundant-test skipping, and a lint rule system that understands node selection.
Fusion is being built to do statically what dbt-core did by asking the warehouse. Catalog-free binding lets SQL bind without introspection, tests get skipped when they are provably redundant, and dbt State speculatively submits nodes while the dependency prefetch is still in flight — all of it trading round-trips for compile-time analysis. Meanwhile 1.x is absorbing the v2 semantic layer YAML piece by piece, which puts metrics and entities into the model graph itself. Adapter breadth keeps widening in parallel, with Databricks service principal auth, Redshift group grants, and ClickHouse materialization configs.
With beta.1 out, the next milestones are further betas hardening the Fusion feature set toward parity, and continued v2 semantic YAML work landing in the 1.x line.
silx releases a couple of times a year and reached 3.0.0 in April 2026, which raised the Python floor to 3.10 and switched the default Qt binding to PySide6. The same release reworked the viewer's data views: 3D scatter support, dedicated RGB(A) image views, the composite ImageView split into Plot2dView and ComplexImageView, and NXdata stacks displayed as images. 3.1.0 has since added asinh axis scaling, the twilight colormaps, and dark-theme icons.
The project is doing a generational refresh of its GUI layer: modern Qt binding, modules broken out of the composite widgets that had accumulated responsibilities, and the theming work that a desktop application needs to look current. Underneath, the recurring fixes are about HDF5 behavior in real facility environments — file locking, NFS refresh, Windows display paths — which is where a synchrotron toolkit actually gets stressed. Feature growth is concentrated in silx view rather than the library API.
Expect the 3.1.x line to keep filling in plotting options and theming, with the PySide6 default flushing out binding-specific bugs from downstream applications over the next few releases.
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 dbt Core or silx.
DoWhy adds one estimation method a year and keeps its identification edge.
OpenHouse is hardening the seams where table policies and jobs quietly fail.
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.
Shiny made reactive apps observable, then gave them a way to tear themselves down
See all dbt Core alternatives → · See all silx alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dbt Core is currently shipping more aggressively (velocity 7.5 vs 2.5), with 2 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. dbt Core is currently shipping more aggressively (velocity 7.5 vs 2.5), with 2 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 dbt Core alternatives in Analytics are ranked by recent ship velocity. Browse the "dbt Core alternatives" section above for the current picks, or visit /alternatives/dbt-core for the full list with editorial commentary on each.
Top silx alternatives in Analytics are ranked by recent ship velocity. Browse the "silx alternatives" section above for the current picks, or visit /alternatives/silx for the full list with editorial commentary on each.