ESPHome
ESPHome ships on a calendar, and the August beta train is now four builds deep.
A side-by-side editorial comparison of b3doc and Dragonfly — release velocity, themes, recent moves, and the top alternatives to consider.
A small B-Cubed utility for turning R Markdown into publishable docs
b3doc converts R Markdown to Markdown and rewrites front matter for documentation published by the B-Cubed project, which is its entire remit. Three releases exist: the initial pair of functions, a generalisation of the front-matter replacement, and a hardening pass that removed regex from the replace argument and standardised figures at 300 DPI. It sits in the b-cubed-eu family alongside impIndicator and shares contributors with the wider Belgian biodiversity tooling group.
Dragonfly spends its releases on correctness in the parts of Redis compatibility nobody tests.
The visible window is almost entirely correctness and internals work on the 1.39/1.40 lines. The newest release consolidates two tiering knobs into a single tiered_max_pending_bytes and exports it to metrics. Behind it sit a memory-accounting backport, a cluster fix that journals FLUSHSLOTS from inside the flush transaction, and a HyperLogLog resync with valkey upstream that pulled in a CVE fix and exposed three Dragonfly-local bugs.
b3doc converts R Markdown to Markdown and rewrites front matter for documentation published by the B-Cubed project, which is its entire remit. Three releases exist: the initial pair of functions, a generalisation of the front-matter replacement, and a hardening pass that removed regex from the replace argument and standardised figures at 300 DPI. It sits in the b-cubed-eu family alongside impIndicator and shares contributors with the wider Belgian biodiversity tooling group.
The direction is toward predictability over flexibility. The replace argument arrived in 0.2.0 generalising the earlier logo-specific behaviour, then 0.3.0 pulled regex support back out of it because escape characters and over-broad matches caused unintended edits. That is a maintainer choosing a narrower tool that fails obviously over a general one that fails quietly — a reasonable trade for a package that rewrites files in place.
Expect continued small releases driven by the documentation pipeline's needs, with output-quality defaults and front-matter handling the likely subjects rather than new functions.
The visible window is almost entirely correctness and internals work on the 1.39/1.40 lines. The newest release consolidates two tiering knobs into a single tiered_max_pending_bytes and exports it to metrics. Behind it sit a memory-accounting backport, a cluster fix that journals FLUSHSLOTS from inside the flush transaction, and a HyperLogLog resync with valkey upstream that pulled in a CVE fix and exposed three Dragonfly-local bugs.
Two threads run through this window. One is upstream parity — the hyperloglog sync explicitly re-forks from valkey and keeps upstream formatting so future syncs stay cheap, which is a maintenance-cost decision as much as a correctness one. The other is the RESP IO loop v2 migration, visible in a pub/sub ordering fix gated on the v1 loop and in tests being skipped on the v1 leg of the regression matrix. Dragonfly is hardening a drop-in Redis replacement in the places where drop-in claims usually break: cluster operations, pub/sub ordering under pipelining, and memory accounting.
Expect continued RESP IO loop v2 work and more upstream syncs on forked Redis internals. The tiering flag consolidation plus its metrics export suggests tiered storage tuning is the next area to get operator-facing surface.
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 b3doc or Dragonfly.
ESPHome ships on a calendar, and the August beta train is now four builds deep.
rapr generalises its Rangeland Analysis Platform API access one endpoint at a time
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 dormant years end with a test fix, not a feature
Four years of releases land in four minutes as the changelog gets backfilled to GitHub
See all b3doc alternatives → · See all Dragonfly alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Dragonfly 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. Dragonfly 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 b3doc alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "b3doc alternatives" section above for the current picks, or visit /alternatives/b3doc for the full list with editorial commentary on each.
Top Dragonfly alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dragonfly alternatives" section above for the current picks, or visit /alternatives/dragonfly for the full list with editorial commentary on each.