RSelenium
RSelenium's only release in eight years touched documentation and CI, nothing else.
A side-by-side editorial comparison of servr and waldo — release velocity, themes, recent moves, and the top alternatives to consider.
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.
waldo keeps shedding dependencies while teaching its diff engine new object systems
waldo produces the object comparisons that testthat failure messages are built from. The recent releases do two things: drop dependencies - tibble, rematch2 and fansi have all gone - and extend comparison to object systems that did not exist when it was written, notably S7. Correctness of missing-value and tolerance semantics accounts for most of the rest.
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.
waldo produces the object comparisons that testthat failure messages are built from. The recent releases do two things: drop dependencies - tibble, rematch2 and fansi have all gone - and extend comparison to object systems that did not exist when it was written, notably S7. Correctness of missing-value and tolerance semantics accounts for most of the rest.
This is a package deliberately shrinking its footprint while widening what it understands. Since it is imported by testthat, every dependency it drops is one fewer package in the check environment of most of CRAN, which is clearly the motivation. The comparison logic itself changes only when R gains a new way to represent objects.
Expect S7 support to deepen from basic to complete as S7 adoption grows, and further dependency removals; the diff algorithm itself looks settled.
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 servr or waldo.
RSelenium's only release in eight years touched documentation and CI, nothing else.
Rhino's release line runs on release candidates, and 1.12 makes room for coding agents.
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.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. servr and waldo 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. servr and waldo 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 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.
Top waldo alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "waldo alternatives" section above for the current picks, or visit /alternatives/waldo for the full list with editorial commentary on each.