distributions3
distributions3 0.3.0 adds sample-based distributions and likelihood derivatives
A side-by-side editorial comparison of esquisse and Plotly — 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.
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
Plotly ships on two tracks. Plotly Studio, the desktop AI app-builder, releases every one to two weeks and has spent v0.0.80 through v0.0.86 on credential handling, reasoning transparency, personalization and now the reliability of the agent session engine itself. Plotly Cloud is the louder track: since late May it has added viewer-seat pricing, domain verification, per-app compute modes with credit-metered billing, and customer-owned domains with managed TLS.
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.
Plotly ships on two tracks. Plotly Studio, the desktop AI app-builder, releases every one to two weeks and has spent v0.0.80 through v0.0.86 on credential handling, reasoning transparency, personalization and now the reliability of the agent session engine itself. Plotly Cloud is the louder track: since late May it has added viewer-seat pricing, domain verification, per-app compute modes with credit-metered billing, and customer-owned domains with managed TLS.
The Cloud releases are assembling the standard pieces of a hosting business in order — identity first (domain verification, explicitly framed as the step before SSO), then billing (viewer seats, then metered compute credits), and now production-grade serving (custom domains, automatic certificate renewal). Studio is being hardened as the authoring front end that feeds it: Universal Deployment pushed beyond Dash apps, credentials saved once and reused, a Winget channel to widen Windows installs, and in v0.0.86 a rebuilt session engine plus automatic retries so agent runs survive expired tokens. The two tracks converge on one funnel — author in Studio, deploy to Cloud, pay by compute consumed.
The Domain Verification entry names SSO as the next step and places it in the Enterprise tier, so single sign-on is the most likely Cloud release next. Studio should hold its one-to-two-week cadence, with the newly added app thumbnails pointing toward more work on browsing and organizing generated apps.
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 Plotly.
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.
Holistics keeps fencing in the AI layer it spent the summer building.
See all esquisse alternatives → · See all Plotly alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Plotly 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. Plotly 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 Plotly alternatives in Analytics are ranked by recent ship velocity. Browse the "Plotly alternatives" section above for the current picks, or visit /alternatives/plotly for the full list with editorial commentary on each.