Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of fable and silx — release velocity, themes, recent moves, and the top alternatives to consider.
fable keeps widening its model shelf, one econometric class at a time
fable is the tidyverts forecasting engine, and its releases are almost entirely about which model families it can express. The 0.4.x line added the vector-error-correction and VARIMA classes plus impulse-response methods; 0.5.0 adds fractional differencing via ARFIMA. Between those, the releases are CRAN-check patches and documentation passes.
silx settles into maintenance a release after its PySide6 migration
silx is in the quiet phase after a generational release. 3.1.1 is a single fix to FitWidget loading a fit function from file. The release before it, 3.1.0, was the first real feature work since the migration - asinh axis scaling, twilight colormaps, and dark-theme icons - and 3.0.1 was similarly small. The 3.0.0 cut that reset the Qt binding and Python floor still defines what the line is doing.
fable is the tidyverts forecasting engine, and its releases are almost entirely about which model families it can express. The 0.4.x line added the vector-error-correction and VARIMA classes plus impulse-response methods; 0.5.0 adds fractional differencing via ARFIMA. Between those, the releases are CRAN-check patches and documentation passes.
The package is closing the gap with the older forecast package's model coverage while keeping the tidy model-specification grammar. Each substantive release is a new model class plus the generate()/IRF() plumbing to make it behave like the existing ones. Maintenance releases cluster around CRAN policy and ggplot2/tsibble compatibility rather than internal rewrites.
Expect the next substantive release to add another model class or extend generate()/IRF() coverage to the classes that still lack them, rather than change the modelling interface.
silx is in the quiet phase after a generational release. 3.1.1 is a single fix to FitWidget loading a fit function from file. The release before it, 3.1.0, was the first real feature work since the migration - asinh axis scaling, twilight colormaps, and dark-theme icons - and 3.0.1 was similarly small. The 3.0.0 cut that reset the Qt binding and Python floor still defines what the line is doing.
The cadence has slowed markedly since April, and the content has shifted from structural change to plotting and colormap refinement. That is the expected shape after a binding migration: downstream beamline code needs a stable target, so the project trades feature velocity for a quiet surface. The gap between 3.0.1 in May and 3.1.0 in August is the clearest signal of the deliberate slowdown.
Expect further point releases servicing the plotting and fitting widgets rather than another structural change, with feature work continuing to arrive in the 3.1.x minors rather than patches.
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 fable or silx.
Omni ships weekly, and almost every week the headline item is an AI feature.
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
aniread stops asking you to know which tracker wrote the file
Rho's release machinery finally produced a stable build — and it shipped no new product.
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
OpenCTI spends a release unblocking queues and hardening upserts
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. silx is currently shipping more aggressively (velocity 5.0 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. silx is currently shipping more aggressively (velocity 5.0 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 fable alternatives in Analytics are ranked by recent ship velocity. Browse the "fable alternatives" section above for the current picks, or visit /alternatives/fable 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.