← Back to home
Comparison · Infra & APIs

Dragonfly vs pkgdown

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

Dragonfly vs pkgdown: at a glance

FeatureDragonflypkgdown
SectorInfra & APIsInfra & APIs
Velocity score5.00.0
Sparks · 30d00
Top themescorrectness, redis-compatibility, cluster, upstream-syncdocumentation, llm-readable, quarto, dark-mode
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 pkgdown?

pkgdown now generates llms.txt and a markdown copy of every documentation page

pkgdown builds the documentation sites for most R packages. The 2.1 line was about format and appearance - Quarto vignettes, a light and dark switch, self-hosted assets instead of CDN fetches. The 2.2 line changed audience: build_llm_docs() emits an llms.txt at the site root and a markdown version of every page, on by default.

Read the full pkgdown trajectory →

Dragonfly vs pkgdown: 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.

P
pkgdown
INFRA · APIS
0.0

pkgdown now generates llms.txt and a markdown copy of every documentation page

◆ Current state

pkgdown builds the documentation sites for most R packages. The 2.1 line was about format and appearance - Quarto vignettes, a light and dark switch, self-hosted assets instead of CDN fetches. The 2.2 line changed audience: build_llm_docs() emits an llms.txt at the site root and a markdown version of every page, on by default.

◆ Where it's heading

Two audiences are now being served from one build. Human-facing work continues in small increments - dark-mode plot filtering, new translations, a local http server so search works in preview - while the new machine-facing output is opt-out rather than opt-in. The default matters more than the feature: thousands of package sites will start emitting llms.txt without their maintainers choosing to.

◆ Prediction

Expect the markdown output to gain the same configuration surface the HTML has, and the llms.txt contents to get more selective as maintainers discover what ends up in it; a way to exclude individual pages is the obvious next request.

Alternatives to Dragonfly and pkgdown

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 pkgdown.

See all Dragonfly alternatives → · See all pkgdown alternatives →

Recent activity from Dragonfly and pkgdown

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 agopkgdownLocal preview served over http so search works
  7. 1mo agoDragonflyi1.39.4: Add list compression tuning flags (#7762)
  8. 9mo agopkgdownbuild_llm_docs() emits llms.txt and markdown for every page
  9. 1y agopkgdownMenu items accept class and id attributes
  10. 1y agopkgdownROR IDs, Codeberg support, bslib navbar variables
  11. 1y agopkgdownKeyboard shortcut for search; clean_cache() added
  12. 2y agopkgdownQuarto vignettes, light/dark switch, self-hosted assets

Frequently asked questions

What is the difference between Dragonfly and pkgdown?

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 pkgdown?

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 pkgdown?

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