RSelenium
RSelenium's only release in eight years touched documentation and CI, nothing else.
A side-by-side editorial comparison of Rhino and servr — release velocity, themes, recent moves, and the top alternatives to consider.
Rhino's release line runs on release candidates, and 1.12 makes room for coding agents.
Rhino publishes only release candidates to this feed — every entry back to 1.9 is an -rc tag, with no final release ever appearing. The 1.12.0 candidate is the first in the window with user-visible substance: a `use` function that scaffolds an AGENTS.md file carrying Rhino-specific instructions, plus a `use` function for the CI template. The rest is maintenance: covr-based test coverage, e2e tests, Node dependency updates, and a maintainer handover.
servr keeps growing from a static file server into a general-purpose R web server.
servr's recent releases add server capability rather than polish: 0.28 introduced HTTP authentication across every server function via an `auth` argument, and 0.29 added `httr()` to execute R scripts and render their output as HTML pages while serving a directory, plus a `response` hook for post-processing. 0.33 moves the directory-listing helpers into xfun so they are shared with `xfun::serve_dir()`, and adds a documentation site. The remaining entries are a WebSocket hash-URL fix and a fallback favicon.
Rhino publishes only release candidates to this feed — every entry back to 1.9 is an -rc tag, with no final release ever appearing. The 1.12.0 candidate is the first in the window with user-visible substance: a `use` function that scaffolds an AGENTS.md file carrying Rhino-specific instructions, plus a `use` function for the CI template. The rest is maintenance: covr-based test coverage, e2e tests, Node dependency updates, and a maintainer handover.
Rhino is converging on scaffolding as its main surface — the framework's value is increasingly in what it generates for you rather than what it does at runtime, and 1.12 extends that generation to instructions meant for AI coding agents rather than humans. The maintainer change and the CI/coverage work in the same release read as consolidation after a long gap: 1.11 shipped in April 2025, 1.12 not until June 2026.
More `use_*` scaffolding functions are the obvious next increment, since two arrived in a single release. Whether the AGENTS.md instructions grow into deeper agent tooling is not something these entries settle.
servr's recent releases add server capability rather than polish: 0.28 introduced HTTP authentication across every server function via an `auth` argument, and 0.29 added `httr()` to execute R scripts and render their output as HTML pages while serving a directory, plus a `response` hook for post-processing. 0.33 moves the directory-listing helpers into xfun so they are shared with `xfun::serve_dir()`, and adds a documentation site. The remaining entries are a WebSocket hash-URL fix and a fallback favicon.
Two threads run through the window. One is capability: auth, script execution, and response post-processing turn what began as a local preview server into something that can serve dynamic, protected content. The other is consolidation — 0.33 pushes shared rendering code up into xfun, thinning servr toward the parts that are actually server-specific. Cadence is slow and irregular; 0.31 to 0.33 spans nearly two years.
More of servr's generic rendering internals are likely to migrate into xfun, given 0.33 set that precedent and the packages share a maintainer.
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 Rhino or servr.
RSelenium's only release in eight years touched documentation and CI, nothing else.
Windmill is dismantling the paywall between itself and the data stack
Resend is wiring itself into every agent runtime it can reach, one standard at a time
vdiffr finished its job in 2021 and has been tracking compilers ever since.
The deployment client is being rebuilt around credentials it never has to store.
A package whose release calendar is written by whoever ships the next Rtools.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Rhino and servr are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. Rhino and servr are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Rhino alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Rhino alternatives" section above for the current picks, or visit /alternatives/rhino-r for the full list with editorial commentary on each.
Top servr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "servr alternatives" section above for the current picks, or visit /alternatives/servr for the full list with editorial commentary on each.