zarr-python
Zarr's package split keeps producing standalone tools: a server, now a lazy indexer.
A side-by-side editorial comparison of httr and magrittr — release velocity, themes, recent moves, and the top alternatives to consider.
httr's last releases are housekeeping - the package now points users at httr2
httr is in wind-down. The last release with real feature work was 1.4.0 in 2018; everything since is test stabilization, CRAN-driven fixes, and unwinding a dependency on the httpbin service. Version 1.4.7 removed the vignette contents outright and redirects readers to httr2.
magrittr rewrote its pipe in C, then base R shipped one and the releases stopped
magrittr gave R the %>% operator and, in 2020, rewrote it in C for speed, lazy evaluation and clean backtraces — explicitly shaped to resemble the pipe R itself was likely to adopt. R 4.1 then shipped |> natively, and magrittr's release history effectively ends: an eager pipe variant in 2.0.2 and a memory-protection fix in 2.0.3, nothing since.
httr is in wind-down. The last release with real feature work was 1.4.0 in 2018; everything since is test stabilization, CRAN-driven fixes, and unwinding a dependency on the httpbin service. Version 1.4.7 removed the vignette contents outright and redirects readers to httr2.
This is a succession, not a decline. The maintainers are keeping httr installable and passing checks for the very large base of packages that depend on it, while all design work happens in httr2. The pattern across these six releases is unambiguous: nothing lands here unless CRAN, a test service, or a platform forced it.
Expect continued patch releases driven only by CRAN checks and toolchain changes; the interesting HTTP work in R will keep landing in httr2.
magrittr gave R the %>% operator and, in 2020, rewrote it in C for speed, lazy evaluation and clean backtraces — explicitly shaped to resemble the pipe R itself was likely to adopt. R 4.1 then shipped |> natively, and magrittr's release history effectively ends: an eager pipe variant in 2.0.2 and a memory-protection fix in 2.0.3, nothing since.
The package's direction was set by its own success. Having proven the idiom and then aligned its semantics with what base R would do, there is little left to add, and the wider ecosystem has been migrating to the native pipe — finetune switched, lintr now requires it by default. magrittr's remaining role is compatibility for the enormous body of code already written against %>%.
The entries do not support a prediction of new features; four years without a release points to a package that is finished rather than one between cycles.
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 httr or magrittr.
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
withr rebuilt defer() on base R's own on.exit(), and got much faster for it
See all httr alternatives → · See all magrittr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. httr and magrittr 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. httr and magrittr 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 httr alternatives in DevOps are ranked by recent ship velocity. Browse the "httr alternatives" section above for the current picks, or visit /alternatives/httr for the full list with editorial commentary on each.
Top magrittr alternatives in DevOps are ranked by recent ship velocity. Browse the "magrittr alternatives" section above for the current picks, or visit /alternatives/magrittr for the full list with editorial commentary on each.