promises
promises drops R6 for plain environments and wires async work into OpenTelemetry
Comparison · DevOps
httpuv vs later
A side-by-side editorial comparison of httpuv and later — release velocity, themes, recent moves, and the top alternatives to consider.
httpuv vs later: at a glance
What is httpuv?
httpuv ships almost nothing, which is what you want from the web server under Shiny
httpuv is the C++ HTTP and WebSocket server that Shiny runs on. Across this window it added exactly one user-facing function - runStaticServer() for serving a directory - and spent every other release on race conditions, compiler and linker changes, CRAN check warnings, and mime type table updates.
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.
httpuv vs later: editorial side-by-side
httpuv
0.0DEVOPS
httpuv ships almost nothing, which is what you want from the web server under Shiny
◆ Current state
httpuv is the C++ HTTP and WebSocket server that Shiny runs on. Across this window it added exactly one user-facing function - runStaticServer() for serving a directory - and spent every other release on race conditions, compiler and linker changes, CRAN check warnings, and mime type table updates.
◆ Where it's heading
There is no direction here in the usual sense, and that is the honest read: the package is a stable foundation whose releases are triggered by the toolchain moving, by R-devel warnings, or by a threading bug surfacing under load. The one recurring theme with substance is connection reliability - WebSocket keepalive pings, race conditions in the I/O thread - which is what actually breaks Shiny apps in production.
◆ Prediction
Expect continued small releases tracking Rtools, R-devel and mime data, with any substantive change most likely coming from a threading or WebSocket issue reported by Shiny users rather than from planned work.
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 httpuv 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 httpuv or later.
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
magrittr
magrittr rewrote its pipe in C, then base R shipped one and the releases stopped
See all httpuv alternatives → · See all later alternatives →
Recent activity from httpuv and later
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 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
- 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
- 1y agohttpuvServes .wasm as application/wasm; mime table refreshed
- 2y agohttpuvrunStaticServer() survives a failed browser launch
- 2y agohttpuvRtools build file update and macOS zlib linking fix
- 2y agohttpuvFixes an R CMD check warning on error format strings
- 2y agohttpuvrunStaticServer() serves a directory of static files
- 3y agohttpuvFixes a race condition introduced in 1.6.10
Frequently asked questions
What is the difference between httpuv and later?
They serve adjacent needs but don't currently overlap on shipped themes. httpuv and later 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.
Is httpuv better than later?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. httpuv and later 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.
What are the best alternatives to httpuv?
Top httpuv alternatives in DevOps are ranked by recent ship velocity. Browse the "httpuv alternatives" section above for the current picks, or visit /alternatives/httpuv 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.