servr
servr keeps growing from a static file server into a general-purpose R web server.
A side-by-side editorial comparison of ESPHome and RSelenium — release velocity, themes, recent moves, and the top alternatives to consider.
ESPHome's August beta opens while the July line keeps absorbing hardware fixes.
ESPHome runs a monthly train and this window covers the tail of 2026.7 plus the opening of the 2026.8 beta. The 2026.7 patches were dominated by field-reported hardware corrections — sensor readings on emc2101, haier and as3935, an ENC28J60 SPI chip-select hold time flagged as breaking, a locked git clone cache so device adoption stops failing on first attempt, and a double-free when the API overflow buffer drain is re-entered. Bundled device-builder and dependabot bumps make up most of the row count in every patch.
RSelenium's only release in eight years touched documentation and CI, nothing else.
1.7.10, published February 2026, contains documentation updates, a move from Travis CI to GitHub Actions, and CRAN note fixes — no functional change at all, and it is the first release since September 2018. The releases before it are equally quiet: a dummy argument in `executeScript`, `phantom()` made defunct, and credential-exposure and driver-startup fixes. The last real capability change in the window is `rsDriver()` arriving in 1.6.4, which replaced the defunct `checkForServer` and `startServer` helpers.
ESPHome runs a monthly train and this window covers the tail of 2026.7 plus the opening of the 2026.8 beta. The 2026.7 patches were dominated by field-reported hardware corrections — sensor readings on emc2101, haier and as3935, an ENC28J60 SPI chip-select hold time flagged as breaking, a locked git clone cache so device adoption stops failing on first attempt, and a double-free when the API overflow buffer drain is re-entered. Bundled device-builder and dependabot bumps make up most of the row count in every patch.
The pattern is stable and worth reading as maturity rather than stagnation: a feature release lands, then three or four patch releases correct the hardware paths that only fail in the field, each one narrow and attributed to a specific board or component. Concurrency and shared-state bugs — the WiFi scan results shared with the captive portal task, the clone cache, the buffer drain — recur often enough to look like the project's current soft spot. The beta tags carry no notes of their own and point at the release changelog instead.
2026.8.0 should reach a stable tag within days given the beta cadence, followed by the usual run of patch releases correcting per-component regressions. What is in it is not visible from these entries, which link out rather than summarize.
1.7.10, published February 2026, contains documentation updates, a move from Travis CI to GitHub Actions, and CRAN note fixes — no functional change at all, and it is the first release since September 2018. The releases before it are equally quiet: a dummy argument in `executeScript`, `phantom()` made defunct, and credential-exposure and driver-startup fixes. The last real capability change in the window is `rsDriver()` arriving in 1.6.4, which replaced the defunct `checkForServer` and `startServer` helpers.
This is a package being kept installable rather than developed. The 2016-2018 era did the architectural work — moving process management out to wdman, recommending Docker for running a Selenium server, retiring PhantomJS — and nothing since has revisited it. That leaves RSelenium sitting on the older WebDriver arrangement while the browser-automation landscape has moved on.
Further releases, if any, are likely to be CRAN-compliance rather than feature work; the entries give no indication of active development resuming.
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 ESPHome or RSelenium.
servr keeps growing from a static file server into a general-purpose R web server.
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.
See all ESPHome alternatives → · See all RSelenium alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. ESPHome is currently shipping more aggressively (velocity 5.0 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. ESPHome is currently shipping more aggressively (velocity 5.0 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 ESPHome alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ESPHome alternatives" section above for the current picks, or visit /alternatives/esphome for the full list with editorial commentary on each.
Top RSelenium alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "RSelenium alternatives" section above for the current picks, or visit /alternatives/rselenium for the full list with editorial commentary on each.