ellipsis
ellipsis' checks live in rlang now; the package is a compatibility shim.
A side-by-side editorial comparison of withr and zarr-python — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Zarr's package split keeps producing standalone tools: a server, now a lazy indexer.
Zarr's Python implementation is being decomposed into standalone packages, with zarr-metadata for the model layer, zarr-indexing for index transforms and zarr-http-server for serving. Each ships on its own version line with its own changelog and documentation site. The most recent activity is zarr-indexing reaching 0.2.0 with LazyArray, followed by a fix to how subpackage docs are built.
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.
Zarr's Python implementation is being decomposed into standalone packages, with zarr-metadata for the model layer, zarr-indexing for index transforms and zarr-http-server for serving. Each ships on its own version line with its own changelog and documentation site. The most recent activity is zarr-indexing reaching 0.2.0 with LazyArray, followed by a fix to how subpackage docs are built.
The split has moved past refactoring into producing capabilities Zarr did not previously have. zarr-http-server 0.1.0 put stores, arrays and groups behind HTTP, and zarr-indexing went from TensorStore-style index transforms in 0.1.0 to generic lazy indexing over the array API in 0.2.0. Supporting infrastructure is being built at the same pace, with towncrier changelogs and per-package docs, which is what the 0.2.1 docs fix is tidying.
Each extracted package has followed its 0.1.0 with a feature release within weeks, so the next move is most likely another zarr-indexing or zarr-http-server increment rather than a change to zarr-python itself.
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 withr or zarr-python.
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
xml2 relicensed to MIT, then moved its hot accessors from S3 into C
See all withr alternatives → · See all zarr-python alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. zarr-python is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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. zarr-python is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
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.
Top zarr-python alternatives in DevOps are ranked by recent ship velocity. Browse the "zarr-python alternatives" section above for the current picks, or visit /alternatives/zarr for the full list with editorial commentary on each.