silx
silx settles into maintenance a release after its PySide6 migration
Comparison · Analytics
TimescaleDB vs vellumplot
A side-by-side editorial comparison of TimescaleDB and vellumplot — release velocity, themes, recent moves, and the top alternatives to consider.
TimescaleDB vs vellumplot: at a glance
What is TimescaleDB?
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.
What is vellumplot?
vellumplot tags its first release with a bet most R grammars don't make: the static figure and the widget are the same object.
A new grammar of graphics built on the vellum vector engine, developing fast — ten releases in roughly three weeks — and now at its first tagged release. The distinguishing architectural claim is that the compiled plot is the scene, so a static export and an interactive widget cannot drift apart, and that it renders without a graphics device because vellum measures text itself. Accessibility is treated as a first-class output rather than an afterthought: tagged PDF with a navigable structure tree and alt text, a plot_lint() check, and colour-vision-deficiency simulation at render time.
TimescaleDB vs vellumplot: editorial side-by-side
TimescaleDB
5.0ANALYTICS
TimescaleDB is paying down correctness debt in its columnstore query paths.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
vellumplot
6.3ANALYTICS
vellumplot tags its first release with a bet most R grammars don't make: the static figure and the widget are the same object.
◆ Current state
A new grammar of graphics built on the vellum vector engine, developing fast — ten releases in roughly three weeks — and now at its first tagged release. The distinguishing architectural claim is that the compiled plot is the scene, so a static export and an interactive widget cannot drift apart, and that it renders without a graphics device because vellum measures text itself. Accessibility is treated as a first-class output rather than an afterthought: tagged PDF with a navigable structure tree and alt text, a plot_lint() check, and colour-vision-deficiency simulation at render time.
◆ Where it's heading
The release sequence shows a grammar filling in ggplot2-parity features and specialist marks in parallel. Parity work landed as secondary axes, rich legend titles, and Sankey styling; the specialist end added categorical datashading, image marks, flow maps and edge bundling for dense graphs. Version 0.7.0 shows a willingness to break early — vsunburst() was removed outright in favour of one vhierarchy() constructor covering sunburst, icicle, treemap and circlepack — which is the right time to do it and suggests the API is still being consolidated toward fewer, more general constructors.
◆ Prediction
Expect more consolidation of near-duplicate constructors under type arguments and continued expansion of the declarative interactivity introduced in 0.7.0, now that the first tagged release has fixed a public API surface.
Alternatives to TimescaleDB and vellumplot
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 TimescaleDB or vellumplot.
Plotly
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
aniread
aniread stops asking you to know which tracker wrote the file
Rho
Rho's release machinery finally produced a stable build — and it shipped no new product.
Usermaven
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
OpenCTI
OpenCTI spends a release unblocking queues and hardening upserts
See all TimescaleDB alternatives → · See all vellumplot alternatives →
Recent activity from TimescaleDB and vellumplot
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoTimescaleDB2.29.2: SkipScan and sparse-index correctness fixes
- 15d agoTimescaleDB2.29.1: security fixes plus compression bugfixes
- 17d agovellumplotFirst tagged release: one spec compiles to PNG, SVG, tagged PDF and a widget ⚡
- 19d agoTimescaleDB2.29.0: chunk exclusion speeds up UPDATE and DELETE
- 23d agovellumplotFlow maps and edge bundling for dense graph plots
- 28d agovellumplotvhierarchy() replaces vsunburst(); declarative interactivity arrives
- 1mo agovellumplotSankey crossing minimisation and per-branch sunburst colouring
- 1mo agovellumplotSecondary axes land; rich legend titles stop clipping
- 1mo agoTimescaleDB2.28.3: columnar pipeline correctness fixes
- 1mo agovellumplotCategorical datashading in one call, plus image marks at data points
- 1mo agoTimescaleDB2.28.2: upgrade-path fixes for 2.28.1
- 1mo agoTimescaleDB2.28.1: compressed-table crash and constraint fixes
Frequently asked questions
What is the difference between TimescaleDB and vellumplot?
They serve adjacent needs but don't currently overlap on shipped themes. vellumplot is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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.
Is TimescaleDB better than vellumplot?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. vellumplot is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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.
What are the best alternatives to TimescaleDB?
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.
What are the best alternatives to vellumplot?
Top vellumplot alternatives in Analytics are ranked by recent ship velocity. Browse the "vellumplot alternatives" section above for the current picks, or visit /alternatives/vellumplot for the full list with editorial commentary on each.