Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of ggplot2 and TimescaleDB — release velocity, themes, recent moves, and the top alternatives to consider.
ggplot2 swapped its object system out from under a decade of downstream code
The 4.0.0 release replaced ggplot2's S3 internals with S7 and made every geom's defaults settable from the theme, both breaking changes. The three releases since have been hotfixes cleaning up the fallout - regressions in geom_area(), position_stack() and the scale and guide systems - plus rlang interoperability repairs. The one genuinely new feature in that window is a quantile.type argument on boxplots.
TimescaleDB is paying down correctness debt in its columnstore query paths.
The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.
The 4.0.0 release replaced ggplot2's S3 internals with S7 and made every geom's defaults settable from the theme, both breaking changes. The three releases since have been hotfixes cleaning up the fallout - regressions in geom_area(), position_stack() and the scale and guide systems - plus rlang interoperability repairs. The one genuinely new feature in that window is a quantile.type argument on boxplots.
This is the tail of a long-telegraphed migration: 3.5.2 existed largely to give downstream packages the is_*() predicates and accessor functions they would need before 4.0 landed. With theme(geom) and from_theme(), styling is consolidating into the theme rather than being repeated per layer, which is the direction the extension ecosystem now has to follow.
Expect further 4.0.x patches as S7-related regressions surface in extension packages, and more of the per-geom default surface to migrate into element_geom(). The entries give no indication of a 4.1 feature line yet.
The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.
The feature work of 2.27 and 2.28 - vectorized filter evaluation, first/last derived straight from columnstore batch metadata, sparse indexes, SkipScan on compressed data - has been followed by a steady stream of fixes to those same code paths. 2.29.2 alone repairs SkipScan dropping uncompressed rows, sparse-index pushdown returning wrong results for IS NULL, and gapfill over window aggregates. That is the normal cost of pushing query optimizations into a compressed columnar store, and the project is working through it release by release rather than pausing.
With three consecutive patch releases on the 2.29 line and no new highlighted features since 2.29.0, the next minor is likely to resume the columnstore performance work - though the density of wrong-results fixes suggests more patches first.
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 ggplot2 or TimescaleDB.
Omni ships weekly, and almost every week the headline item is an AI feature.
silx settles into maintenance a release after its PySide6 migration
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.
See all ggplot2 alternatives → · See all TimescaleDB alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. TimescaleDB 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. TimescaleDB 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 ggplot2 alternatives in Analytics are ranked by recent ship velocity. Browse the "ggplot2 alternatives" section above for the current picks, or visit /alternatives/ggplot2 for the full list with editorial commentary on each.
Top TimescaleDB alternatives in Analytics are ranked by recent ship velocity. Browse the "TimescaleDB alternatives" section above for the current picks, or visit /alternatives/timescaledb for the full list with editorial commentary on each.