httpuv
httpuv ships almost nothing, which is what you want from the web server under Shiny
Comparison · DevOps
distributed vs httr
A side-by-side editorial comparison of distributed and httr — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:maintenance
distributed vs httr: at a glance
What is distributed?
Dask's scheduler spent the year deleting deprecated API, not adding surface.
distributed is cutting frequent tags with little in them. The substantive release in the window is 2026.6.0, which removed deprecations across the scheduler, worker, nanny, CLI, security and deploy modules in roughly twenty separate cleanups and moved CI to pixi. 2026.7.0 follows with a breaking scatter change and a scheduler_info() default change; the two most recent tags are a backport and an empty release with no changes at all.
What is httr?
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.
distributed vs httr: editorial side-by-side
distributed
5.0DEVOPS
Dask's scheduler spent the year deleting deprecated API, not adding surface.
◆ Current state
distributed is cutting frequent tags with little in them. The substantive release in the window is 2026.6.0, which removed deprecations across the scheduler, worker, nanny, CLI, security and deploy modules in roughly twenty separate cleanups and moved CI to pixi. 2026.7.0 follows with a breaking scatter change and a scheduler_info() default change; the two most recent tags are a backport and an empty release with no changes at all.
◆ Where it's heading
The direction is consolidation. A single maintainer is systematically retiring API that had been deprecated for years, tightening type annotations and chasing flaky tests, while the feature surface stays flat. Python 3.14 support and a PyArrow floor in 2026.1.2 fit the same pattern of keeping the runtime current rather than extending it.
◆ Prediction
With the deprecation sweep largely done and pixi now driving CI, the next releases most likely continue as small breaking cleanups on top of a stable feature set rather than introducing new scheduler capability.
httr
0.0DEVOPS
httr's last releases are housekeeping - the package now points users at httr2
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
Expect continued patch releases driven only by CRAN checks and toolchain changes; the interesting HTTP work in R will keep landing in httr2.
Alternatives to distributed and httr
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 distributed or httr.
promises
promises drops R6 for plain environments and wires async work into OpenTelemetry
withr
withr rebuilt defer() on base R's own on.exit(), and got much faster for it
htmltools
htmltools spends three releases walking back its own fill-layout opinions
xml2
xml2 relicensed to MIT, then moved its hot accessors from S3 into C
magrittr
magrittr rewrote its pipe in C, then base R shipped one and the releases stopped
See all distributed alternatives → · See all httr alternatives →
Recent activity from distributed and httr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agodistributedBackport tag extending an earlier fix
- 1mo agodistributedEmpty release: no changes
- 1mo agodistributedBreaking: scatter stops unpacking custom containers
- 2mo agodistributedDeprecated APIs removed across scheduler, worker and CLI
- 4mo agodistributedCI pins, type hints and a dashboard CPU fix
- 6mo agodistributedPython 3.14 support and a PyArrow 16 floor
- 2y agohttrVignettes removed and redirected to httr2 ⚡
- 3y agohttrStops using the httpbin service in examples and tests
- 3y agohttrOut-of-band auth helper honors the rlang_interactive option
- 3y agohttrFixes an intermittent test failure
- 6y agohttrparse_url() follows RFC3986 for scheme parsing
- 7y agohttrDrops the Windows CA bundle override so curl uses schannel
Frequently asked questions
What is the difference between distributed and httr?
Both compete on the same themes — maintenance — within DevOps. distributed 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.
Is distributed better than httr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. distributed 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 DevOps products to evaluate alongside.
What are the best alternatives to distributed?
Top distributed alternatives in DevOps are ranked by recent ship velocity. Browse the "distributed alternatives" section above for the current picks, or visit /alternatives/dask-distributed for the full list with editorial commentary on each.
What are the best alternatives to httr?
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.