Windmill
Windmill is dismantling the paywall between itself and the data stack
Comparison · Infra & APIs
Dragonfly vs pkgbuild
A side-by-side editorial comparison of Dragonfly and pkgbuild — release velocity, themes, recent moves, and the top alternatives to consider.
Dragonfly vs pkgbuild: 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 pkgbuild?
A package whose release calendar is written by whoever ships the next Rtools.
pkgbuild is the layer devtools and pak use to run R CMD build and R CMD INSTALL, and most of what it does is know where the compiler is. Six of its last eight releases are about Rtools: supporting Rtools43, 44 and 45, finding installations that did not come from an installer, reading the Windows registry correctly again, and handling aarch64 Windows when the expected environment variable is unset. The feature surface is a handful of Config/build/* DESCRIPTION options for packages with unusual build needs.
Dragonfly vs pkgbuild: 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.
pkgbuild
0.0INFRA · APIS
A package whose release calendar is written by whoever ships the next Rtools.
◆ Current state
pkgbuild is the layer devtools and pak use to run R CMD build and R CMD INSTALL, and most of what it does is know where the compiler is. Six of its last eight releases are about Rtools: supporting Rtools43, 44 and 45, finding installations that did not come from an installer, reading the Windows registry correctly again, and handling aarch64 Windows when the expected environment variable is unset. The feature surface is a handful of Config/build/* DESCRIPTION options for packages with unusual build needs.
◆ Where it's heading
This is maintenance defined entirely by other people's release schedules — R minor versions, Rtools versions, and the DESCRIPTION options downstream package authors ask for. The one structural change worth noting is that on R 4.3 and later the package stopped special-casing Windows and now tests for build tools by compiling a small package, the same way it always has on Unix. That is the direction: fewer platform branches, more probing.
◆ Prediction
Expect the next release to add support for whichever Rtools ships alongside the next R minor version, and expect the Windows registry lookups to keep shrinking as the compile-probe approach proves out.
Alternatives to Dragonfly and pkgbuild
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 pkgbuild.
Resend
Resend is wiring itself into every agent runtime it can reach, one standard at a time
vdiffr
vdiffr finished its job in 2021 and has been tracking compilers ever since.
rsconnect
The deployment client is being rebuilt around credentials it never has to store.
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 pkgbuild alternatives →
Recent activity from Dragonfly and pkgbuild
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 agopkgbuildnever-clean build option; aarch64 Windows Rtools detection
- 1y agopkgbuildWindows build-tool detection now probes by compiling
- 1y agopkgbuildFix Rtools 4.3 and 4.4 discovery on Windows
- 2y agopkgbuildSupport R 4.4.x and Rtools44
- 2y agopkgbuildDrops crayon, rprojroot and prettyunits dependencies
- 3y agopkgbuildbootstrap.R now runs under pkgbuild_process and pak
Frequently asked questions
What is the difference between Dragonfly and pkgbuild?
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 pkgbuild?
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 pkgbuild?
Top pkgbuild alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "pkgbuild alternatives" section above for the current picks, or visit /alternatives/pkgbuild for the full list with editorial commentary on each.