zarr-python
Zarr's package split keeps producing standalone tools: a server, now a lazy indexer.
A side-by-side editorial comparison of cpp11 and withr — release velocity, themes, recent moves, and the top alternatives to consider.
cpp11 has spent two years rebuilding itself on R's supported API surface
cpp11 is the header-only C++ interface for R packages, and nearly every release in this window is governed by one force: R core's tightening of what counts as non-API. 0.5.0 removed the growable-vector internals that made push_back() cheap, 0.5.3 and 0.5.4 removed further non-API usage, and the small releases in between are crash and compiler-warning fixes.
withr rebuilt defer() on base R's own on.exit(), and got much faster for it
withr provides the with_ and local_ functions that temporarily change global state and restore it on exit - the cleanup primitive under most of the tidyverse test suites. Version 3.0.0 reimplemented defer() as a thin wrapper over base::on.exit(), which the maintainers made possible by contributing the required arguments to R 3.5 itself. Everything since has been small correctness work.
cpp11 is the header-only C++ interface for R packages, and nearly every release in this window is governed by one force: R core's tightening of what counts as non-API. 0.5.0 removed the growable-vector internals that made push_back() cheap, 0.5.3 and 0.5.4 removed further non-API usage, and the small releases in between are crash and compiler-warning fixes.
The package is trading a little performance for the right to keep passing CRAN checks indefinitely, and saying so plainly in the release notes. With R >= 4.0 now required, whole compatibility branches have been deleted rather than maintained. The remaining work is narrow: finish the non-API migration, then get back to interface features like cpp_source() handling multiple files.
Expect the last non-API dependencies to be cleared and the deprecated compatibility defines to be removed outright; the entries suggest maintenance discipline rather than new C++ surface.
withr provides the with_ and local_ functions that temporarily change global state and restore it on exit - the cleanup primitive under most of the tidyverse test suites. Version 3.0.0 reimplemented defer() as a thin wrapper over base::on.exit(), which the maintainers made possible by contributing the required arguments to R 3.5 itself. Everything since has been small correctness work.
The arc here is a package pushing its own machinery down into base R and then living off the result. Once defer() became on.exit(), the remaining work is about where cleanup is allowed to happen - knitr documents, source() calls, the global environment, session end - and about restoring state correctly when an expression exits early. Releases are now infrequent and CRAN-driven.
Expect continued low-volume releases fixing edge cases in where deferred handlers run; with the core delegated to base R, there is little left that would prompt a larger change.
Other DevOps 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 cpp11 or withr.
Zarr's package split keeps producing standalone tools: a server, now a lazy indexer.
ellipsis' checks live in rlang now; the package is a compatibility shim.
clock is turning calendar conventions lubridate hard-coded into parameterized types.
httpuv ships almost nothing, which is what you want from the web server under Shiny
promises drops R6 for plain environments and wires async work into OpenTelemetry
htmltools spends three releases walking back its own fill-layout opinions
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — performance — within DevOps. cpp11 and withr 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. cpp11 and withr 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 DevOps products to evaluate alongside.
Top cpp11 alternatives in DevOps are ranked by recent ship velocity. Browse the "cpp11 alternatives" section above for the current picks, or visit /alternatives/cpp11 for the full list with editorial commentary on each.
Top withr alternatives in DevOps are ranked by recent ship velocity. Browse the "withr alternatives" section above for the current picks, or visit /alternatives/withr for the full list with editorial commentary on each.