accessr
One R Markdown source, four accessible formats — and a fortnight spent patching around someone else's bug.
A side-by-side editorial comparison of g6R and rwasm — release velocity, themes, recent moves, and the top alternatives to consider.
An R binding whose releases are mostly the upstream JS graph engine arriving, plus port ergonomics.
g6R wraps AntV's G6 graph engine as an htmlwidget, with Shiny proxy functions for data updates, layout control and mouse position read-back. The current release bundles G6 5.1.1 and ships the widget as a single self-contained bundle, having removed the split chunk. Recent work has concentrated on ports, the connection points nodes expose, with a new label-bottom placement, a larger default radius and a quieter hover state.
The toolchain that gets R packages into the browser is optimising for payload size, not features.
rwasm cross-compiles R packages to WebAssembly and assembles the virtual filesystem images that webR loads. Its three releases have moved from making cross-compilation work at all — Autoconf overrides, uname and pkg-config shims, OpenMP support — to controlling how the resulting artefacts are packaged and shipped. Every release is pinned to a specific webR version floor.
g6R wraps AntV's G6 graph engine as an htmlwidget, with Shiny proxy functions for data updates, layout control and mouse position read-back. The current release bundles G6 5.1.1 and ships the widget as a single self-contained bundle, having removed the split chunk. Recent work has concentrated on ports, the connection points nodes expose, with a new label-bottom placement, a larger default radius and a quieter hover state.
Two threads run through the record. One is upstream tracking: the 0.6.5 engine bump alone restored the SVG renderer, fixed a combo-related canvas crash and pulled in new node and edge query APIs, which is a lot of user-visible change that this package did not author. The other is R-side ergonomics, where ports have been reworked in three consecutive releases and 0.5.0 added data validation strict enough that the notes warn existing code may break. Layout behaviour has moved toward explicit control, with recomputation now opt-in via an option and a dedicated proxy function.
The port work looks unfinished given three releases in a row on it, so more placement and styling options are the likeliest next step, alongside another engine bump as G6 5.1.x moves. Nothing in these entries indicates a direction beyond keeping pace with upstream.
rwasm cross-compiles R packages to WebAssembly and assembles the virtual filesystem images that webR loads. Its three releases have moved from making cross-compilation work at all — Autoconf overrides, uname and pkg-config shims, OpenMP support — to controlling how the resulting artefacts are packaged and shipped. Every release is pinned to a specific webR version floor.
The arc runs from correctness to delivery. The first release fought the cross-compilation environment itself, isolating builds from host libraries and shimming the tools configure scripts expect. The second replaced Emscripten's own file_packager with a custom metadata path and added gzip compression for filesystem images. The third is pure coordination, rebuilding the build system for webR 0.5.0. That cadence — roughly annual, each release gated on a webR version — makes this a component of the webR release train rather than an independently moving project.
The next release will most likely follow the next webR version, since two of three releases so far have been driven by a webR floor rather than by rwasm's own agenda.
Other Infra & APIs 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 g6R or rwasm.
One R Markdown source, four accessible formats — and a fortnight spent patching around someone else's bug.
The R package that installs Java for you stopped needing an update every time Java ships.
A young ML metrics package rewrote its own backend twice in six months chasing speed.
The AusTraits engine, generalised for anyone's trait database, now links measurements to real specimens.
Fail2Ban finally ships 1.1.1 after 14 months in beta, with a botched deb package on the way out the door
A logging header for Rcpp packages that sat untouched for nine years, then changed how it switches on
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. g6R is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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. g6R is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top g6R alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "g6R alternatives" section above for the current picks, or visit /alternatives/g6r for the full list with editorial commentary on each.
Top rwasm alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rwasm alternatives" section above for the current picks, or visit /alternatives/rwasm for the full list with editorial commentary on each.