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 Dashy and rwasm — release velocity, themes, recent moves, and the top alternatives to consider.
A release per merged PR, and right now nearly every one is a translation string.
Dashy cuts a version tag for each merged pull request, so the changelog reads at commit granularity. The current run is almost entirely localisation and dependency work — Traditional Chinese completed, hard-coded strings extracted, German added for the edit-item dialog — broken only by a mobile search fix and two grouped dependency bumps.
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.
Dashy cuts a version tag for each merged pull request, so the changelog reads at commit granularity. The current run is almost entirely localisation and dependency work — Traditional Chinese completed, hard-coded strings extracted, German added for the edit-item dialog — broken only by a mobile search fix and two grouped dependency bumps.
The project is in maintenance rhythm: no feature work in this window, and the one substantive thread is making the UI translatable by pulling hard-coded strings out so contributors can localise them. That extraction is what enabled the German and Chinese contributions that follow it, which is the only causal chain visible in the feed.
Expect more single-PR patch tags in the same mix — further language contributions now that strings are extracted, plus dependabot groups. Nothing in these entries points to a feature release.
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 Dashy 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. Dashy is currently shipping more aggressively (velocity 6.3 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. Dashy is currently shipping more aggressively (velocity 6.3 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 Dashy alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dashy alternatives" section above for the current picks, or visit /alternatives/dashy 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.