vdiffr
vdiffr finished its job in 2021 and has been tracking compilers ever since.
A side-by-side editorial comparison of ESPHome and highr — 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.
highr is finished software: one-line releases every year or two
highr does syntax highlighting for knitr output, and every release in this window is a single line of change. The most recent wraps hilight() output in xfun::raw_string() for nicer printing; before that, a rename of two LaTeX command macros and two bumps to the minimum R version. There is no feature work here at all.
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.
highr does syntax highlighting for knitr output, and every release in this window is a single line of change. The most recent wraps hilight() output in xfun::raw_string() for nicer printing; before that, a rename of two LaTeX command macros and two bumps to the minimum R version. There is no feature work here at all.
This is a completed micro-package in the knitr ecosystem, maintained only to stay installable and consistent with its parent packages. Changes are triggered by knitr's needs or CRAN's requirements rather than by any plan of its own, and the gaps between releases run to years.
Expect the next release whenever knitr or CRAN requires one, with a similarly single-line changelog.
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 highr.
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.
DNSControl v5 is feature complete and counting down to an August ship date
git2r stopped vendoring libgit2 and now expects it on the system
casdoor ships several times a day, mostly tightening organization boundaries.
See all ESPHome alternatives → · See all highr 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 highr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "highr alternatives" section above for the current picks, or visit /alternatives/highr for the full list with editorial commentary on each.