Windmill
Windmill is dismantling the paywall between itself and the data stack
Comparison · Infra & APIs
Dragonfly vs vdiffr
A side-by-side editorial comparison of Dragonfly and vdiffr — release velocity, themes, recent moves, and the top alternatives to consider.
Dragonfly vs vdiffr: at a glance
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.
What is vdiffr?
vdiffr finished its job in 2021 and has been tracking compilers ever since.
vdiffr generates deterministic SVG snapshots so plot changes show up as test failures. Its recent history is almost entirely toolchain: UCRT Windows compatibility twice, a revert to C++11 to work around a GCC issue, and renaming the internal SVG device so it stops colliding with svglite. The only functional additions in view are snapshot variants in 1.0.8 and a testthat fix so snapshots are no longer auto-deleted when a test errors or skips. The last release was October 2024.
Dragonfly vs vdiffr: editorial side-by-side
Dragonfly
5.0INFRA · APIS
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.
vdiffr
0.0INFRA · APIS
vdiffr finished its job in 2021 and has been tracking compilers ever since.
◆ Current state
vdiffr generates deterministic SVG snapshots so plot changes show up as test failures. Its recent history is almost entirely toolchain: UCRT Windows compatibility twice, a revert to C++11 to work around a GCC issue, and renaming the internal SVG device so it stops colliding with svglite. The only functional additions in view are snapshot variants in 1.0.8 and a testthat fix so snapshots are no longer auto-deleted when a test errors or skips. The last release was October 2024.
◆ Where it's heading
The package reached its intended shape at 1.0.0, when snapshot management moved to testthat and vdiffr shed most of its own R and JavaScript code to become a reproducible SVG engine and nothing more. There is not much left to add to that, and the release stream since reads accordingly: it moves when a compiler, an R version, or testthat moves. For a testing dependency this is a healthy end state, though it does mean the package inherits whatever the graphics engine does to snapshot stability.
◆ Prediction
The entries do not support predicting a feature release. The likely next change is a compatibility fix prompted by a compiler or a testthat change, as every release since 1.0.2 has been.
Alternatives to Dragonfly and vdiffr
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 vdiffr.
Resend
Resend is wiring itself into every agent runtime it can reach, one standard at a time
rsconnect
The deployment client is being rebuilt around credentials it never has to store.
pkgbuild
A package whose release calendar is written by whoever ships the next Rtools.
DNSControl
DNSControl v5 is feature complete and counting down to an August ship date
highr
highr is finished software: one-line releases every year or two
See all Dragonfly alternatives → · See all vdiffr alternatives →
Recent activity from Dragonfly and vdiffr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoDragonflyBackported memory-accounting fix; FLUSHSLOTS journaled in-transaction
- 14d agoDragonflyi1.39.11: chore(hll): sync hyperloglog.c with valkey upstream (#7961)
- 20d agoDragonflyFix mutable cross-thread access on shared reply builder
- 22d agoDragonflyi1.39.9: fix(facade): preserve pub/sub order on unsubscribe (v1 IO loop) (#7909)
- 1mo agoDragonflyi1.39.6: test: skip V2-only pause tests under V1 (#7822)
- 1mo agoDragonflyi1.39.4: Add list compression tuning flags (#7762)
- 1y agovdiffrSnapshot variants supported
- 2y agovdiffrRevert to C++11 for a GCC workaround
- 2y agovdiffrRename internal SVG device to avoid svglite collision
- 4y agovdiffrUCRT Windows compatibility under Rtools42
- 4y agovdiffrUCRT Windows compatibility
- 5y agovdiffrSnapshots survive errored and skipped tests
Frequently asked questions
What is the difference between Dragonfly and vdiffr?
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 vdiffr?
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 vdiffr?
Top vdiffr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "vdiffr alternatives" section above for the current picks, or visit /alternatives/vdiffr for the full list with editorial commentary on each.