httpuv
httpuv ships almost nothing, which is what you want from the web server under Shiny
Comparison · DevOps
distributed vs later
A side-by-side editorial comparison of distributed and later — release velocity, themes, recent moves, and the top alternatives to consider.
distributed vs later: 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 later?
later spends its releases keeping R's event loop compiling against moving toolchains.
later provides the event loop that lets R schedule callbacks, underpinning shiny, httpuv and most async work in the language. Recent releases are overwhelmingly build and compatibility work: Rcpp error-handling changes, a C23 namespace collision with glibc, and header ordering to satisfy Rcpp auto-includes.
distributed vs later: 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.
later
0.0DEVOPS
later spends its releases keeping R's event loop compiling against moving toolchains.
◆ Current state
later provides the event loop that lets R schedule callbacks, underpinning shiny, httpuv and most async work in the language. Recent releases are overwhelmingly build and compatibility work: Rcpp error-handling changes, a C23 namespace collision with glibc, and header ordering to satisfy Rcpp auto-includes.
◆ Where it's heading
The API is settled enough that the release calendar is set by the surrounding ecosystem rather than by any feature plan. 1.4.5 cleaned house by dropping pre-unwind-protect fallbacks, and 1.4.6 carries the only recent change a user would notice at all — lower CPU use when idle at the console.
◆ Prediction
Expect further releases pinned to compiler and Rcpp changes, with the observable surface staying essentially where it is.
Alternatives to distributed and later
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 later.
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
httr
httr's last releases are housekeeping - the package now points users at httr2
See all distributed alternatives → · See all later alternatives →
Recent activity from distributed and later
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
- 5mo agolaterlater 1.4.8 tracks Rcpp Rf_error handling changes
- 5mo agolaterlater 1.4.7 fixes a C23 once_flag collision breaking builds
- 6mo agolaterlater 1.4.6 improves idle responsiveness at the R console
- 6mo agodistributedPython 3.14 support and a PyArrow 16 floor
- 7mo agolaterlater 1.4.5 drops legacy fallbacks, requires R 3.5 and Rcpp 1.0.10
- 11mo agolaterlater 1.4.4 fixes test timings only
- 11mo agolaterlater 1.4.3 stops touching .Random.seed, drops autorun argument
Frequently asked questions
What is the difference between distributed and later?
They serve adjacent needs but don't currently overlap on shipped themes. 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 later?
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 later?
Top later alternatives in DevOps are ranked by recent ship velocity. Browse the "later alternatives" section above for the current picks, or visit /alternatives/later-r for the full list with editorial commentary on each.