Casdoor
casdoor ships several times a day, mostly tightening organization boundaries.
A side-by-side editorial comparison of Dragonfly and waldo — release velocity, themes, recent moves, and the top alternatives to consider.
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.
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.
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.
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.
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.
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.
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.
Expect S7 support to deepen from basic to complete as S7 adoption grows, and further dependency removals; the diff algorithm itself looks settled.
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.
casdoor ships several times a day, mostly tightening organization boundaries.
downlit's HTML contract was set in 0.4.0; every release since tracks R itself.
dittodb has spent four years on CRAN link fixes and one DBI bump.
connectapi is becoming the scripted administration surface for Posit Connect.
chromote turned the browser itself into a pinned, downloadable dependency.
lifecycle gave the tidyverse the word superseded, then spent years tuning who gets warned
See all Dragonfly alternatives → · See all waldo 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 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.
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.