Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of spiro and Rho — release velocity, themes, recent moves, and the top alternatives to consider.
Cardiopulmonary exercise test data in R, one metabolic cart vendor at a time.
spiro imports and processes cardiopulmonary exercise testing data in R, handling the file formats that metabolic carts from Cosmed, Cortex, Vyntus, and ZAN emit, then interpolating, smoothing, and summarizing them into comparable variables. The bulk of ongoing work is vendor format compatibility rather than analysis features — 0.2.4 fixed Cosmed imports failing in rare cases and Cortex imports on newer devices, and 0.2.2 added English-language Vyntus files after 0.1.2 added French ones. The analysis side, spiro_max(), spiro_smooth() and spiro_plot(), has been stable for some time.
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.
spiro imports and processes cardiopulmonary exercise testing data in R, handling the file formats that metabolic carts from Cosmed, Cortex, Vyntus, and ZAN emit, then interpolating, smoothing, and summarizing them into comparable variables. The bulk of ongoing work is vendor format compatibility rather than analysis features — 0.2.4 fixed Cosmed imports failing in rare cases and Cortex imports on newer devices, and 0.2.2 added English-language Vyntus files after 0.1.2 added French ones. The analysis side, spiro_max(), spiro_smooth() and spiro_plot(), has been stable for some time.
This is a mature rOpenSci package whose remaining work is dictated by other people's file formats. Each device firmware revision, each regional language variant, and each ggplot2 release generates maintenance, and that is what fills the changelog. The API itself settled early, with the 0.1.0 rOpenSci review pass renaming the protocol helpers to the pt_* prefix and 0.2.0 replacing the confusingly named spiro_import() with spiro_raw().
Expect the pattern to continue: import fixes as vendor formats shift and periodic plotting updates tracking ggplot2, with no indication of new analysis capability.
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 spiro or Rho.
Omni ships weekly, and almost every week the headline item is an AI feature.
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
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 spiro alternatives in Analytics are ranked by recent ship velocity. Browse the "spiro alternatives" section above for the current picks, or visit /alternatives/spiro 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.