dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
A side-by-side editorial comparison of inbotheme and TimescaleDB — release velocity, themes, recent moves, and the top alternatives to consider.
An institutional ggplot2 theme in slow maintenance, tracking upstream deprecations.
INBOtheme supplies ggplot2 themes and colour palettes matching the house style of INBO and the Flemish government. The current release is compatibility work: silencing ggplot2 deprecation warnings, quieting an interactive palette message, and refreshing the shared checklist tooling INBO uses across its packages. The substantive palette work happened two years earlier.
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.
INBOtheme supplies ggplot2 themes and colour palettes matching the house style of INBO and the Flemish government. The current release is compatibility work: silencing ggplot2 deprecation warnings, quieting an interactive palette message, and refreshing the shared checklist tooling INBO uses across its packages. The substantive palette work happened two years earlier.
Development is reactive rather than directional — the package changes when ggplot2 changes or when institutional branding does. The 0.6.0 release reworked palettes and split the documentation; since then the only movement has been keeping that surface valid against upstream deprecations. Note that the feed is not strictly chronological, with 0.5.7 published after 0.5.8.
The next release is most likely another ggplot2 compatibility pass; a branding refresh would be the only plausible trigger for anything larger, and nothing in these entries signals one.
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 inbotheme or TimescaleDB.
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
Holistics keeps fencing in the AI layer it spent the summer building.
Dovetail spent July opening doors to other tools and August making its own rooms easier to enter.
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
AgencyAI got skills three weeks ago; everything since has been making them routine.
See all inbotheme 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 inbotheme alternatives in Analytics are ranked by recent ship velocity. Browse the "inbotheme alternatives" section above for the current picks, or visit /alternatives/inbotheme 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.