← Back to home
Comparison · Infra & APIs

Dragonfly vs waldo

A side-by-side editorial comparison of Dragonfly and waldo — release velocity, themes, recent moves, and the top alternatives to consider.

Dragonfly vs waldo: at a glance

FeatureDragonflywaldo
SectorInfra & APIsInfra & APIs
Velocity score5.00.0
Sparks · 30d00
Top themescorrectness, redis-compatibility, cluster, upstream-synctesting, diffing, dependencies, s7
Last editorial update9h ago1h ago
WebsiteVisit →Visit →

What is Dragonfly?

Dragonfly is spending its releases on correctness debt, not features.

The last two months are almost entirely correctness work: a pub/sub ordering bug that silently discarded queued messages on unsubscribe, a multi-key PFCOUNT that read sixteen wrong registers, an uninitialized pointer in the sparse HyperLogLog promote path, and now cluster FLUSHSLOTS that was not journaled inside its own flush transaction. The one structural move is the resync of the forked hyperloglog.c against valkey upstream, which cut divergence from 2,139 lines to 767 and pulled in a CVE fix plus AVX2 and NEON merge kernels. New user-facing options are rare; the list compression tuning flags are the exception.

Read the full Dragonfly trajectory →

What is waldo?

waldo keeps shedding dependencies while teaching its diff engine new object systems

waldo produces the object comparisons that testthat failure messages are built from. The recent releases do two things: drop dependencies - tibble, rematch2 and fansi have all gone - and extend comparison to object systems that did not exist when it was written, notably S7. Correctness of missing-value and tolerance semantics accounts for most of the rest.

Read the full waldo trajectory →

Dragonfly vs waldo: editorial side-by-side

D
Dragonfly
INFRA · APIS
5.0

Dragonfly is spending its releases on correctness debt, not features.

◆ Current state

The last two months are almost entirely correctness work: a pub/sub ordering bug that silently discarded queued messages on unsubscribe, a multi-key PFCOUNT that read sixteen wrong registers, an uninitialized pointer in the sparse HyperLogLog promote path, and now cluster FLUSHSLOTS that was not journaled inside its own flush transaction. The one structural move is the resync of the forked hyperloglog.c against valkey upstream, which cut divergence from 2,139 lines to 767 and pulled in a CVE fix plus AVX2 and NEON merge kernels. New user-facing options are rare; the list compression tuning flags are the exception.

◆ Where it's heading

Two threads run in parallel. One reduces the cost of carrying a Redis fork by re-syncing individual files against valkey and leaving provenance notes so the next sync is cheap. The other hardens the V2 IO loop while the V1 path still takes the fixes — several commits explicitly defer the V2 half of a fix to a later change, so the two loops are not at parity. Cluster correctness around slot migration and journaling is the newest front.

◆ Prediction

The deferred V2 IO-loop fixes are the obvious next commits, and more forked Redis files are likely to get the same upstream resync treatment now that the pattern and its accounting are established.

W
waldo
INFRA · APIS
0.0

waldo keeps shedding dependencies while teaching its diff engine new object systems

◆ Current state

waldo produces the object comparisons that testthat failure messages are built from. The recent releases do two things: drop dependencies - tibble, rematch2 and fansi have all gone - and extend comparison to object systems that did not exist when it was written, notably S7. Correctness of missing-value and tolerance semantics accounts for most of the rest.

◆ Where it's heading

This is a package deliberately shrinking its footprint while widening what it understands. Since it is imported by testthat, every dependency it drops is one fewer package in the check environment of most of CRAN, which is clearly the motivation. The comparison logic itself changes only when R gains a new way to represent objects.

◆ Prediction

Expect S7 support to deepen from basic to complete as S7 adoption grows, and further dependency removals; the diff algorithm itself looks settled.

Alternatives to Dragonfly and waldo

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 Dragonfly or waldo.

See all Dragonfly alternatives → · See all waldo alternatives →

Recent activity from Dragonfly and waldo

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoDragonflyBackported memory-accounting fix; FLUSHSLOTS journaled in-transaction
  2. 14d agoDragonflyi1.39.11: chore(hll): sync hyperloglog.c with valkey upstream (#7961)
  3. 20d agoDragonflyFix mutable cross-thread access on shared reply builder
  4. 22d agoDragonflyi1.39.9: fix(facade): preserve pub/sub order on unsubscribe (v1 IO loop) (#7909)
  5. 1mo agoDragonflyi1.39.6: test: skip V2-only pause tests under V1 (#7822)
  6. 1mo agoDragonflyi1.39.4: Add list compression tuning flags (#7762)
  7. 1y agowaldoCompares weakrefs, ignores read-only S7 properties
  8. 1y agowaldoOnly uses bit64 comparison when bit64 is installed
  9. 1y agowaldoDrops tibble and rematch2; adds basic S7 support
  10. 1y agowaldoDrops the fansi dependency
  11. 2y agowaldoFixes for upcoming R-devel changes
  12. 3y agowaldoTolerance now governs both display and NaN equality

Frequently asked questions

What is the difference between Dragonfly and waldo?

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.

Is Dragonfly better than waldo?

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.

What are the best alternatives to Dragonfly?

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.

What are the best alternatives to waldo?

Top waldo alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "waldo alternatives" section above for the current picks, or visit /alternatives/waldo for the full list with editorial commentary on each.