Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of deeptime and TimescaleDB — release velocity, themes, recent moves, and the top alternatives to consider.
A geologic-time plotting layer that outgrew time axes and became a geology rendering toolkit.
deeptime extends ggplot2 with geological time scales, radial deep-time coordinates and phylogeny-aware geoms, and since 2.0.0 it also renders standardized FGDC/USGS geologic patterns as ggplot2 fills. The current 2.4.0 release adds geom_text_clade() for labeling clades on radial phylogenies and repairs long-standing coord_trans_xy() and scale-placement edge cases.
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.
deeptime extends ggplot2 with geological time scales, radial deep-time coordinates and phylogeny-aware geoms, and since 2.0.0 it also renders standardized FGDC/USGS geologic patterns as ggplot2 fills. The current 2.4.0 release adds geom_text_clade() for labeling clades on radial phylogenies and repairs long-standing coord_trans_xy() and scale-placement edge cases.
The package is converging on two jobs: being the canonical R renderer for stratigraphic drawing conventions, and keeping pace with ggplot2's own churn. A sustained deprecation program — gggeo_scale(), coord_geo_polar(), getScaleData(), now disparity_through_time() — is trimming the surface down to coord_geo(), coord_geo_radial() and the pattern functions. Roughly half of each recent release is ggplot2 4.0 compatibility work.
Expect disparity_through_time() and coord_geo_polar() to be removed outright in the next major version, and further geoms aimed at annotating radial phylogenies.
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 deeptime 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 deeptime 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 deeptime alternatives in Analytics are ranked by recent ship velocity. Browse the "deeptime alternatives" section above for the current picks, or visit /alternatives/deeptime-r 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.