tidyr
tidyr replaced separate() with a family that says what it does.
A side-by-side editorial comparison of ApexCharts and modeltime — release velocity, themes, recent moves, and the top alternatives to consider.
Three releases in three weeks moved ApexCharts from free library to gated open-core.
ApexCharts is shipping the v6 line at an unusual clip — ten releases since 20 July, spanning a plugin platform, a hybrid SVG/canvas renderer, and two new chart types. The core is still zero-dependency and SVG-first, and every release states that existing configs render unchanged. What is new is a commercial layer: an offline licence check now sits over seven premium modules and one chart type, while the free catalogue keeps expanding alongside it.
modeltime built conformal intervals in, then went quiet on features.
modeltime is at 1.3.3, a single change making the package robust to xgboost version shifts. The feature weight sits in 1.3.2, which added a future-based parallel backend, the maape() accuracy metric and dials helpers for ADAM engine tuning, and further back in the 1.2.8 and 1.3.0 pair that introduced conformal prediction intervals and then carried them through the nested forecasting workflow.
ApexCharts is shipping the v6 line at an unusual clip — ten releases since 20 July, spanning a plugin platform, a hybrid SVG/canvas renderer, and two new chart types. The core is still zero-dependency and SVG-first, and every release states that existing configs render unchanged. What is new is a commercial layer: an offline licence check now sits over seven premium modules and one chart type, while the free catalogue keeps expanding alongside it.
The commercialisation arc tightens one notch per release. 6.5.0 introduced licensing with a watermark and an explicit promise that no chart type would be gated; 6.6.0 gated one; 6.7.0 changed enforcement from accepting any valid key to requiring an entitled plan. Running underneath is a genuine engineering push — incremental updateSeries, canvas cell rendering, a numeric fast path for line and area — that makes the paid layer easier to justify. The pattern is a generous free core with the new authoring and analysis surface behind a key.
Expect more premium chart types following `unit`, since the gating machinery and trial-mode watermark are now built and proven. The shared key format across the apex* family suggests entitlement checks propagate to the sibling libraries next.
modeltime is at 1.3.3, a single change making the package robust to xgboost version shifts. The feature weight sits in 1.3.2, which added a future-based parallel backend, the maape() accuracy metric and dials helpers for ADAM engine tuning, and further back in the 1.2.8 and 1.3.0 pair that introduced conformal prediction intervals and then carried them through the nested forecasting workflow.
The arc runs from uncertainty quantification to execution. Conformal intervals arrived first and were then threaded through nested fitting, refitting and the printed forecast tables so users can see which confidence method produced an interval. The later work moves down a layer to how forecasts are computed — a portable future backend replacing foreach tuning — rather than what they express.
With only an xgboost compatibility fix since the 1.3.2 feature release, the entries do not support a confident prediction about what comes next beyond continued dependency maintenance.
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 ApexCharts or modeltime.
tidyr replaced separate() with a family that says what it does.
performance keeps adding ways to check a model you have already fitted.
CmdStanPy is clearing deprecations ahead of a 2.0 it keeps announcing.
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.
See all ApexCharts alternatives → · See all modeltime alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. ApexCharts is currently shipping more aggressively (velocity 10.0 vs 0.0), with 3 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. ApexCharts is currently shipping more aggressively (velocity 10.0 vs 0.0), with 3 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 ApexCharts alternatives in Analytics are ranked by recent ship velocity. Browse the "ApexCharts alternatives" section above for the current picks, or visit /alternatives/apexcharts for the full list with editorial commentary on each.
Top modeltime alternatives in Analytics are ranked by recent ship velocity. Browse the "modeltime alternatives" section above for the current picks, or visit /alternatives/modeltime for the full list with editorial commentary on each.