Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of forecast and silx — release velocity, themes, recent moves, and the top alternatives to consider.
After years of pure maintenance, forecast 9.0.0 reopens the package
forecast is the long-established R forecasting package that fable was meant to succeed. For several years its releases were RNG fixes, base-R compatibility and documentation. Then 9.0.0 arrived with a batch of new model constructors, wider prediction-interval support and a rewritten accuracy() built on S3 methods.
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.
forecast is the long-established R forecasting package that fable was meant to succeed. For several years its releases were RNG fixes, base-R compatibility and documentation. Then 9.0.0 arrived with a batch of new model constructors, wider prediction-interval support and a rewritten accuracy() built on S3 methods.
The major version reframes forecast around explicit *_model() constructors — mean, random walk, spline, theta, Croston — rather than the older function-per-method style, and the 9.0.x patches since have been performance and argument-handling cleanups on top. That is an active maintenance line, not a package winding down in favour of fable.
Expect continued 9.0.x patches consolidating the new constructors and their forecast methods, with the older interfaces kept working alongside them.
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 forecast 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
See all forecast 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. 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 forecast alternatives in Analytics are ranked by recent ship velocity. Browse the "forecast alternatives" section above for the current picks, or visit /alternatives/forecast-r 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.