Windmill
Windmill is dismantling the paywall between itself and the data stack
A side-by-side editorial comparison of pkgbuild and waldo — release velocity, themes, recent moves, and the top alternatives to consider.
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.
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.
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.
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.
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.
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 pkgbuild or waldo.
Windmill is dismantling the paywall between itself and the data stack
Resend is wiring itself into every agent runtime it can reach, one standard at a time
vdiffr finished its job in 2021 and has been tracking compilers ever since.
The deployment client is being rebuilt around credentials it never has to store.
DNSControl v5 is feature complete and counting down to an August ship date
highr is finished software: one-line releases every year or two
See all pkgbuild alternatives → · See all waldo alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — maintenance — within Infra & APIs. pkgbuild and waldo are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. pkgbuild and waldo are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
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.
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.