RSelenium
RSelenium's only release in eight years touched documentation and CI, nothing else.
Comparison · Infra & APIs
ESPHome vs Rhino
A side-by-side editorial comparison of ESPHome and Rhino — release velocity, themes, recent moves, and the top alternatives to consider.
ESPHome vs Rhino: at a glance
What is ESPHome?
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.
What is Rhino?
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.
ESPHome vs Rhino: editorial side-by-side
ESPHome
5.0INFRA · APIS
ESPHome's August beta opens while the July line keeps absorbing hardware fixes.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Rhino
0.0INFRA · APIS
Rhino's release line runs on release candidates, and 1.12 makes room for coding agents.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to ESPHome and Rhino
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 Rhino.
servr
servr keeps growing from a static file server into a general-purpose R web server.
Windmill
Windmill is dismantling the paywall between itself and the data stack
Resend
Resend is wiring itself into every agent runtime it can reach, one standard at a time
vdiffr
vdiffr finished its job in 2021 and has been tracking compilers ever since.
rsconnect
The deployment client is being rebuilt around credentials it never has to store.
See all ESPHome alternatives → · See all Rhino alternatives →
Recent activity from ESPHome and Rhino
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 18h agoESPHome2026.8.0 beta 2 tagged
- 1d agoESPHome2026.8.0 beta 1 opens the August cycle
- 8d agoESPHomeDevice adoption and API buffer fixes land in 2026.7.4
- 16d agoESPHomeENC28J60 SPI timing fix, flagged as a breaking change
- 21d agoESPHomesen5x gains a model override; MIPI SPI partial update fixed
- 23d agoESPHomeSensor reading fixes across emc2101, haier and as3935
- 2mo agoRhinoRhino 1.12 adds AGENTS.md and CI-template scaffolding
- 1y agoRhinoRhino 1.11.0 release candidate
- 1y agoRhinoRhino 1.10.0 release candidate
- 2y agoRhinoRhino 1.9 adds bslib support and prettier formatting
Frequently asked questions
What is the difference between ESPHome and Rhino?
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.
Is ESPHome better than Rhino?
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.
What are the best alternatives to ESPHome?
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.
What are the best alternatives to Rhino?
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.