silx
silx settles into maintenance a release after its PySide6 migration
Comparison · Analytics
ribd vs TimescaleDB
A side-by-side editorial comparison of ribd and TimescaleDB — release velocity, themes, recent moves, and the top alternatives to consider.
ribd vs TimescaleDB: at a glance
What is ribd?
The pedsuite's coefficient engine: broadening what it computes, then making the plots publishable.
ribd computes relatedness coefficients from pedigrees, covering kinship, inbreeding, kappa, condensed and detailed identity coefficients, and two-locus versions of several of these, in autosomal and X-chromosomal form. The IBD triangle is now drawable in base graphics, ggplot2 or plotly, with an optional inset pedigree, and custom relationships can be placed on it. The most recent release is dominated by correctness work, fixing pair ordering and row alignment in coefficient tables and edge cases for pedigree lists, unrelated individuals and self-pairs.
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.
ribd vs TimescaleDB: editorial side-by-side
ribd
2.5ANALYTICS
The pedsuite's coefficient engine: broadening what it computes, then making the plots publishable.
◆ Current state
ribd computes relatedness coefficients from pedigrees, covering kinship, inbreeding, kappa, condensed and detailed identity coefficients, and two-locus versions of several of these, in autosomal and X-chromosomal form. The IBD triangle is now drawable in base graphics, ggplot2 or plotly, with an optional inset pedigree, and custom relationships can be placed on it. The most recent release is dominated by correctness work, fixing pair ordering and row alignment in coefficient tables and edge cases for pedigree lists, unrelated individuals and self-pairs.
◆ Where it's heading
The arc runs from generality to presentation to precision. Early releases replaced narrow functions with general ones, most visibly when gKinship() absorbed generalisedKinship() and identityCoefs() superseded the separate autosomal and X-chromosomal identity functions in favour of an Xchrom argument. The middle stretch turned the IBD triangle into a proper plotting surface across three graphics systems. The current phase reads as consolidation, with the newest release listing six bug fixes against four features, several of them alignment errors in output tables, which is where a coefficient library most needs to be exactly right.
◆ Prediction
The two new internal functions in the latest release, inbreedingContributions() and ancestralKinship(), are the kind of thing that surfaces publicly a release or two later, so expect them to become exported decomposition tools. The correctness push through pedigree lists and edge cases suggests the near-term focus stays on hardening rather than new coefficient families.
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.
Alternatives to ribd and TimescaleDB
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 ribd or TimescaleDB.
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 ribd alternatives → · See all TimescaleDB alternatives →
Recent activity from ribd and TimescaleDB
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
- 15d agoribdCustom relationships on the IBD triangle; six alignment and edge-case fixes
- 19d agoTimescaleDB2.29.0: chunk exclusion speeds up UPDATE and DELETE
- 1mo agoTimescaleDB2.28.3: columnar pipeline correctness fixes
- 1mo agoTimescaleDB2.28.2: upgrade-path fixes for 2.28.1
- 1mo agoTimescaleDB2.28.1: compressed-table crash and constraint fixes
- 1y agoribdkappaIBD() can skip across-component pairs on large pedigrees
- 2y agoribdIBD triangle plots gain ggplot2 and plotly backends, plus inset pedigrees
- 3y agoribdTriangle line clipping, automatic plot margins, citation info
- 3y agoribdTwo-locus functions overhauled; twoLocusInbreeding and ELR added
- 4y agoribdIdentity coefficients unified behind identityCoefs() and an Xchrom argument
Frequently asked questions
What is the difference between ribd and TimescaleDB?
They serve adjacent needs but don't currently overlap on shipped themes. TimescaleDB is currently shipping more aggressively (velocity 5.0 vs 2.5), 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.
Is ribd better than TimescaleDB?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. TimescaleDB is currently shipping more aggressively (velocity 5.0 vs 2.5), 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.
What are the best alternatives to ribd?
Top ribd alternatives in Analytics are ranked by recent ship velocity. Browse the "ribd alternatives" section above for the current picks, or visit /alternatives/ribd for the full list with editorial commentary on each.
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.