whirl
whirl turned script logging into a standardized provenance artifact regulators can read.
A side-by-side editorial comparison of ESPHome and portfoliobacktest — release velocity, themes, recent moves, and the top alternatives to consider.
ESPHome ships on a calendar, and the August beta train is now four builds deep.
ESPHome runs a monthly release train with a beta series ahead of each version. The 2026.7 line closed out with four patch releases covering sensor correctness and build-system behaviour — a device adoption failure caused by concurrent clone cache resolution, ESP-IDF honouring compile process limits, wider C++ source globbing and a lock on WiFi scan results shared with the captive portal. The 2026.8 cycle is now at its fourth beta, with the substance still behind the beta changelog site rather than in the feed.
Four dormant years end with a test fix, not a feature
portfolioBacktest runs portfolio strategies across multiple datasets and resampled windows, producing performance tables, leaderboards and charts. After a run of substantive releases through 2021 and early 2022 it went quiet for four years. The May 2026 release does one thing: fix unit tests against a breaking change in PerformanceAnalytics::Return.portfolio(), which now returns results for the full input series rather than only from the first weight date.
ESPHome runs a monthly release train with a beta series ahead of each version. The 2026.7 line closed out with four patch releases covering sensor correctness and build-system behaviour — a device adoption failure caused by concurrent clone cache resolution, ESP-IDF honouring compile process limits, wider C++ source globbing and a lock on WiFi scan results shared with the captive portal. The 2026.8 cycle is now at its fourth beta, with the substance still behind the beta changelog site rather than in the feed.
The cadence is the product. Betas arrive every day or two as bump merges carrying no notes, the final release points at a changelog URL, and the real detail lands in the patch releases that follow it. That makes the feed a poor guide to what actually changed in any given month — the 2026.7 patches are the only entries here with readable content, and they are dominated by per-component fixes from a wide set of outside contributors plus automated dependency and device-builder bumps.
Expect 2026.8.0 to go final within days of the beta series ending, followed by the usual run of patch releases carrying the per-component fixes that the beta entries never described.
portfolioBacktest runs portfolio strategies across multiple datasets and resampled windows, producing performance tables, leaderboards and charts. After a run of substantive releases through 2021 and early 2022 it went quiet for four years. The May 2026 release does one thing: fix unit tests against a breaking change in PerformanceAnalytics::Return.portfolio(), which now returns results for the full input series rather than only from the first weight date.
The development work is behind it. The 2019 to 2022 releases built the substance — parallel execution, resampling that works beyond stock data and beyond daily bars, transaction-cost-aware designs through w_current, and a switch from compounded to uncompounded returns in the Sharpe and annualized return calculations. Since then the package has moved only when a dependency forced it, and even then only far enough to keep the tests green.
Nothing in the entries suggests planned work; the next release is most likely triggered by another dependency change, on the same four-year-gap pattern.
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 portfoliobacktest.
whirl turned script logging into a standardized provenance artifact regulators can read.
rapr generalises its Rangeland Analysis Platform API access one endpoint at a time
A small B-Cubed utility for turning R Markdown into publishable docs
An R interface to GeoPackage that keeps sanding down its own API
R's logging package handed to new maintainers and rebuilt from the inside out
Four years of releases land in four minutes as the changelog gets backfilled to GitHub
See all ESPHome alternatives → · See all portfoliobacktest 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 portfoliobacktest alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "portfoliobacktest alternatives" section above for the current picks, or visit /alternatives/portfoliobacktest for the full list with editorial commentary on each.