silx
silx settles into maintenance a release after its PySide6 migration
A side-by-side editorial comparison of rstatix and Rho — release velocity, themes, recent moves, and the top alternatives to consider.
rstatix hit 1.0 by unrounding every p-value it has ever returned
rstatix is the pipe-friendly test wrapper behind most ggpubr annotation workflows — t-tests, Wilcoxon, ANOVA, post-hoc comparisons, effect sizes, all returning tidy data frames. After three quiet years of CRAN-compat patching, it shipped 1.0.0 and 1.1.0 three weeks apart in mid-2026. Both releases push in the same direction: interval estimates and full-precision output for numbers the package previously rounded or omitted.
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.
rstatix is the pipe-friendly test wrapper behind most ggpubr annotation workflows — t-tests, Wilcoxon, ANOVA, post-hoc comparisons, effect sizes, all returning tidy data frames. After three quiet years of CRAN-compat patching, it shipped 1.0.0 and 1.1.0 three weeks apart in mid-2026. Both releases push in the same direction: interval estimates and full-precision output for numbers the package previously rounded or omitted.
The work is about matching what dedicated effect-size packages give you without taking on their dependencies. Confidence intervals for partial eta squared and for Cohen's d are both computed in base R from noncentral distributions and both check against effectsize; compact letter displays are computed in base R against multcompView. The pattern is deliberate — reproduce the reference implementation, add no imports. Alongside that, the package has started correcting statistical hygiene it got wrong for years, most visibly by no longer rounding p-values before adjusting them.
The analytic-interval machinery now exists for eta squared and Cohen's d; the untouched effect sizes in the package — eta squared for nonparametric tests, Cramer's V, rank-biserial correlation — are the obvious next targets for the same base-R noncentral treatment.
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 rstatix 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
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 2.5), 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 2.5), 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 rstatix alternatives in Analytics are ranked by recent ship velocity. Browse the "rstatix alternatives" section above for the current picks, or visit /alternatives/rstatix 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.