Delta Lake
A 4.4.0 tag appears, but the feed carries only its release plumbing
A side-by-side editorial comparison of esquisse and Rho — release velocity, themes, recent moves, and the top alternatives to consider.
esquisse's 1.0 turned a point-and-click addin into embeddable Shiny modules.
The visible history covers the 1.0 line only. 1.0.0 is the substantial one: modules for importing data (via datamods) and exporting plots, a `ggplot_output()` / `render_ggplot()` pair, manual colour palettes, aesthetic parameter selection, more export formats including pptx, and typography controls. 1.0.1 and 1.0.2 are corrective — sf object handling, package-sourced data, disabled-panel label controls, and an `output_format` argument on the save modal.
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.
The visible history covers the 1.0 line only. 1.0.0 is the substantial one: modules for importing data (via datamods) and exporting plots, a `ggplot_output()` / `render_ggplot()` pair, manual colour palettes, aesthetic parameter selection, more export formats including pptx, and typography controls. 1.0.1 and 1.0.2 are corrective — sf object handling, package-sourced data, disabled-panel label controls, and an `output_format` argument on the save modal.
The arc runs from a self-contained RStudio addin toward a component library other people build with: once plot rendering and export exist as Shiny modules, esquisse's ggplot builder can be dropped inside someone else's app rather than only launched beside RStudio. The two follow-up releases are consolidation on that surface rather than expansion of it.
Further work most likely lands on the module API and export coverage, since that is where 1.0.0 put the new surface and where 1.0.2 already returned. The entries do not indicate anything about cadence beyond this line.
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 esquisse or Rho.
A 4.4.0 tag appears, but the feed carries only its release plumbing
distributions3 0.3.0 adds sample-based distributions and likelihood derivatives
Basedash keeps pushing its data out of the workspace — now to people without accounts
RStudio ships through release branches, and the notes are commit messages
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
See all esquisse 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 esquisse alternatives in Analytics are ranked by recent ship velocity. Browse the "esquisse alternatives" section above for the current picks, or visit /alternatives/esquisse 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.