Liquidsoap
Liquidsoap opens its 2.5 line with subtitles as a first-class content type and a streaming server of its own
A side-by-side editorial comparison of odbc and Prometheus — release velocity, themes, recent moves, and the top alternatives to consider.
odbc keeps turning into an authentication broker with a database driver attached.
odbc is DBI's ODBC backend, and the releases in view are dominated by three vendors. Databricks, Snowflake and Redshift each got a dedicated connection helper, and the work since has been almost entirely about credentials: OAuth, viewer-based identity on Posit Connect, service principals, workload identity federation, private keys passed from memory. The plain driver work — DATETIMEOFFSET on SQL Server, DB2 XML, Oracle date writes, an interrupt that no longer crashes — runs underneath in a steady stream of point releases.
Prometheus 3.14 ships the release candidate unchanged, duration expressions now on by default
3.14.0 is byte-identical to the 3.14.0-rc.0 body published a week earlier, so the stable cut carries exactly what the candidate previewed: PromQL duration expressions enabled by default with the feature flag retired, first_over_time promoted to stable, Oracle Cloud service discovery added, and a set of start-timestamp experiments still behind flags. The performance work is the substantive half, with regex matchers on literal alternations, native histogram scrape parsing down roughly 49% in allocations, and a recursion-free text parser that closes a stack-overflow path on hostile exposition.
odbc is DBI's ODBC backend, and the releases in view are dominated by three vendors. Databricks, Snowflake and Redshift each got a dedicated connection helper, and the work since has been almost entirely about credentials: OAuth, viewer-based identity on Posit Connect, service principals, workload identity federation, private keys passed from memory. The plain driver work — DATETIMEOFFSET on SQL Server, DB2 XML, Oracle date writes, an interrupt that no longer crashes — runs underneath in a steady stream of point releases.
The centre of the package has moved from talking to a database to proving who you are to a warehouse. Version 1.7.0 makes that explicit by handing Snowflake connection resolution to the snowflakeauth package so odbc reads the vendor's own connections.toml rather than defining its own parameter set. That is a pattern worth watching: as each warehouse standardises its config across CLI, Python and R, odbc's job shifts from inventing an interface to conforming to one.
Expect Databricks to get the same treatment Snowflake just received — configuration resolved from the vendor's own config files rather than from odbc arguments — and expect the deprecated odbcConnection* functions to be removed outright.
3.14.0 is byte-identical to the 3.14.0-rc.0 body published a week earlier, so the stable cut carries exactly what the candidate previewed: PromQL duration expressions enabled by default with the feature flag retired, first_over_time promoted to stable, Oracle Cloud service discovery added, and a set of start-timestamp experiments still behind flags. The performance work is the substantive half, with regex matchers on literal alternations, native histogram scrape parsing down roughly 49% in allocations, and a recursion-free text parser that closes a stack-overflow path on hostile exposition.
The project is spending its feature budget on start timestamps, appearing across PromQL, TSDB encoding, and remote write V2 in the same release but held behind use-start-timestamps and histograms-st-encoding. Everything else follows the established rhythm of promoting one experimental function per cycle and adding a cloud discovery source. The API deprecations are being staged carefully, warning now and rejecting at the next major.
Start timestamps are the obvious candidate to lose their feature flags once the encoding and remote-write halves have run together, and the stats parameter values now warned on will be rejected in the next major.
Other DevOps 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 odbc or Prometheus.
Liquidsoap opens its 2.5 line with subtitles as a first-class content type and a streaming server of its own
Appwrite keeps reworking its own plumbing — Go CLI, SquashFS mounts, and an MCP layer that refreshes itself
FusionAuth's feed publishes version numbers; whether they carry news is a coin flip.
Sanity ships across every package at once, and the agent-facing surface moves fastest.
The 6.1 candidate arrives carrying the same notes the beta already shipped in June.
Auth0 hands tenants a throttle on their own noisy apps
See all odbc alternatives → · See all Prometheus alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Prometheus 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. Prometheus 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 DevOps products to evaluate alongside.
Top odbc alternatives in DevOps are ranked by recent ship velocity. Browse the "odbc alternatives" section above for the current picks, or visit /alternatives/odbc-r for the full list with editorial commentary on each.
Top Prometheus alternatives in DevOps are ranked by recent ship velocity. Browse the "Prometheus alternatives" section above for the current picks, or visit /alternatives/prometheus for the full list with editorial commentary on each.