silx
silx settles into maintenance a release after its PySide6 migration
A side-by-side editorial comparison of TLF-Library and Rho — release velocity, themes, recent moves, and the top alternatives to consider.
The Open Systems Pharmacology plotting layer spent 2025 absorbing a ggplot2 major break.
tlf is the plotting library behind Open Systems Pharmacology's tables, listings and figures — a ggplot2 wrapper producing the PK/PD reporting output the OSP suite generates. Recent work splits into two strands: a feature set adding Lower Limit Of Quantification annotation to time-profile and observed-vs-predicted plots alongside a reworked axis-limits API, and then hot fixes to survive ggplot2 v4.0.0's breaking changes. The axis change is the substantive one, separating cropping the view from filtering the data behind it.
Rho's release machinery finally produced a stable build — and it shipped no new product.
Rho is an R IDE that has just moved from an all-prerelease train to a stable 0.4.0, and its public feed remains almost entirely release engineering. The one substantive entry, 0.4.0-dev.39, described capability-based model routing across providers and durable project-scoped agent conversations with per-file Apply/Undo. The releases since then have been distribution work: a signed automatic updater shared across Windows, macOS and Linux, then the stable build that packages it.
tlf is the plotting library behind Open Systems Pharmacology's tables, listings and figures — a ggplot2 wrapper producing the PK/PD reporting output the OSP suite generates. Recent work splits into two strands: a feature set adding Lower Limit Of Quantification annotation to time-profile and observed-vs-predicted plots alongside a reworked axis-limits API, and then hot fixes to survive ggplot2 v4.0.0's breaking changes. The axis change is the substantive one, separating cropping the view from filtering the data behind it.
The library is maturing into a stable reporting dependency rather than growing new plot types — the newest releases are watermark placement, log-tick safety and upstream compatibility, not new figures. Its exposure is to ggplot2: v4.0.0 required same-day hot fixes, which is the risk profile of a wrapper this thin. Note that this feed's version numbers and publication stamps disagree, with 1.5.170 stamped four months before the lower-numbered 1.5.158, so the release order has to be read from version numbers and the changelog ranges rather than from the feed order.
With the ggplot2 v4 fallout patched and the LLOQ work promoted to a stable 1.6 line, the next releases most likely continue as small rendering fixes. Nothing in these entries points to a new plot class in progress.
Rho is an R IDE that has just moved from an all-prerelease train to a stable 0.4.0, and its public feed remains almost entirely release engineering. The one substantive entry, 0.4.0-dev.39, described capability-based model routing across providers and durable project-scoped agent conversations with per-file Apply/Undo. The releases since then have been distribution work: a signed automatic updater shared across Windows, macOS and Linux, then the stable build that packages it.
The project is building an agentic R IDE but publishing like a regulated release process: signed evidence, checksums bound to exact commits, and limitations named out loud rather than buried. That discipline has now paid off in the only way it could — 0.4.0 stable ships a Windows installer, a notarized macOS disk image and a Linux AppImage that can all update themselves, with failed verification preserving the running version. The feed's long-standing pattern of dev.NN builds with no final has broken; feature work and shipping work were on separate tracks, and the shipping track arrived first.
With distribution solved, the next entry that matters is the first one describing product capability again rather than packaging. The unresolved item these releases name themselves is Windows trust: the installer is still signed with a SignPath Free Trial self-signed certificate that SmartScreen may warn on.
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 TLF-Library or Rho.
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
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
OpenCTI spends a release unblocking queues and hardening upserts
Mimir's feed is a weekly Helm bot, with the 3.2 candidate the only real release in months
See all TLF-Library alternatives → · See all Rho alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Rho is currently shipping more aggressively (velocity 6.3 vs 0.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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Rho is currently shipping more aggressively (velocity 6.3 vs 0.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.
Top TLF-Library alternatives in Analytics are ranked by recent ship velocity. Browse the "TLF-Library alternatives" section above for the current picks, or visit /alternatives/tlf-library for the full list with editorial commentary on each.
Top Rho alternatives in Analytics are ranked by recent ship velocity. Browse the "Rho alternatives" section above for the current picks, or visit /alternatives/yulab-smu-rho for the full list with editorial commentary on each.