silx
silx settles into maintenance a release after its PySide6 migration
A side-by-side editorial comparison of glyfun and TimescaleDB — release velocity, themes, recent moves, and the top alternatives to consider.
glyfun is three releases old and has spent all of them chasing glyexp's container change.
glyfun is the newest glycoverse package, carved out to hold the enrichment analysis functions that glystats deprecated. Its entire visible history is the 0.1.x series, and all three releases are container plumbing: detected_universe() learning to accept GlycoproteomicSE, then the vignette and documentation following. There is no independent feature work in the record yet.
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.
glyfun is the newest glycoverse package, carved out to hold the enrichment analysis functions that glystats deprecated. Its entire visible history is the 0.1.x series, and all three releases are container plumbing: detected_universe() learning to accept GlycoproteomicSE, then the vignette and documentation following. There is no independent feature work in the record yet.
This is a package being born into a migration rather than one navigating it. Because glystats removed its gly_enrich_*() functions outright and glysmith already routes enrichment through glyfun, the functional surface is inherited rather than designed here. The near-term arc is catching up to the rest of the stack; the interesting question is what glyfun adds once it is no longer just the relocation target.
Expect the first release with genuinely new enrichment capability rather than migration plumbing, most likely broadening the gene-set sources glystats never covered.
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 glyfun or TimescaleDB.
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.
OpenCTI spends a release unblocking queues and hardening upserts
See all glyfun 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 glyfun alternatives in Analytics are ranked by recent ship velocity. Browse the "glyfun alternatives" section above for the current picks, or visit /alternatives/glyfun 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.