lstar
A single-cell data store commits to Zarr v3 and range-readable hosting across four language surfaces
A side-by-side editorial comparison of haze and Rho — release velocity, themes, recent moves, and the top alternatives to consider.
Four dormant years end with a modernization pass and an off-by-one fix in the C++ core
haze does nearest-neighbour smoothing and k-d tree interpolation on brain surface meshes. It sat untouched from April 2022 until July 2026, when a single release modernized it for current R versions and corrected an off-by-one error in the C++ code. It is not on CRAN and never will be — the package exceeds 50MB against CRAN's 5MB ceiling, a constraint its own initial release notes acknowledge.
Rho's release machinery is now more rigorous than the product it ships.
Rho is an R IDE in open prerelease, and its public feed is 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. Everything around it is build candidates and acceptance targets, each gated behind an explicit acceptance record that fails closed.
haze does nearest-neighbour smoothing and k-d tree interpolation on brain surface meshes. It sat untouched from April 2022 until July 2026, when a single release modernized it for current R versions and corrected an off-by-one error in the C++ code. It is not on CRAN and never will be — the package exceeds 50MB against CRAN's 5MB ceiling, a constraint its own initial release notes acknowledge.
The July 2026 release arrived 56 minutes after its sibling regfusionr 0.3.0 from the same maintainer, which is the tell: this is a maintainer sweeping a set of related neuroimaging packages back into working order, not independent development on haze itself. haze is the dependency, regfusionr the consumer, and the substantive work sits on the regfusionr side. The off-by-one correction is the only change here that alters results.
Expect haze to move only when a downstream dfsp-spirit package needs it to — its cadence is driven by the sibling packages, not by its own roadmap.
Rho is an R IDE in open prerelease, and its public feed is 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. Everything around it is build candidates and acceptance targets, each gated behind an explicit acceptance record that fails closed.
The project is building an agentic R IDE but publishing like a regulated release process: signed evidence, CONDITIONAL_GO records, checksums bound to exact commits, limitations named out loud rather than buried. dev.41 exists solely to rehearse the native updater across Windows and macOS, which is the last piece of distribution infrastructure between a dev train and something installable by people who won't build from source. Feature work and shipping work are advancing on separate tracks.
The updater acceptance target points at a 0.4.0 line that can update itself, so the next entry that matters is either dev.40's real publication or the first build not labelled evaluation-only. Whether Windows signing moves off the SignPath trial certificate is the open question these entries leave unanswered.
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 haze or Rho.
A single-cell data store commits to Zarr v3 and range-readable hosting across four language surfaces
Text analysis in R keeps optimising its token internals — and builds a path out to torch
The ModernDive teaching package learns to render inside the browser that runs its own textbook
A GPU-accelerated Bayesian GLM package buys its way into the standard R Bayesian toolchain
USGS puts a type system over its river network toolkit so errors surface at dispatch
The chromatography file-format translator keeps absorbing vendor formats one release at a time
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 haze alternatives in Analytics are ranked by recent ship velocity. Browse the "haze alternatives" section above for the current picks, or visit /alternatives/haze 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.