httpuv
httpuv ships almost nothing, which is what you want from the web server under Shiny
Comparison · DevOps
httr2 vs later
A side-by-side editorial comparison of httr2 and later — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r
httr2 vs later: at a glance
What is httr2?
httr2 is growing production concerns: tracing, throttling and token hygiene.
httr2 is the tidyverse's modern HTTP client and the designated successor to httr. Recent releases have moved past request-building ergonomics into operational concerns — OpenTelemetry traces for every request, throttling that behaves correctly across repeated calls, and a fix for OAuth token caches that were never actually being pruned.
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.
httr2 vs later: editorial side-by-side
httr2
2.5DEVOPS
httr2 is growing production concerns: tracing, throttling and token hygiene.
◆ Current state
httr2 is the tidyverse's modern HTTP client and the designated successor to httr. Recent releases have moved past request-building ergonomics into operational concerns — OpenTelemetry traces for every request, throttling that behaves correctly across repeated calls, and a fix for OAuth token caches that were never actually being pruned.
◆ Where it's heading
The package is maturing into infrastructure for long-running R services rather than interactive scripts. The 1.2.0 lifecycle purge removed deprecated streaming and mocking APIs in favour of a connection-based model, and debugging affordances like httr2_translate() point at users who need to reproduce a failing request outside R.
◆ Prediction
Expect further observability and credential-handling work, with the rlang-driven cache hash change in 1.3.0 likely to surface follow-up issues as existing caches silently invalidate.
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 httr2 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 httr2 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
Recent activity from httr2 and later
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agohttr2httr2 1.3.0 fixes OAuth token caches that never expired
- 1mo agohttr2httr2 1.2.3 translates requests into curl commands
- 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
- 8mo agohttr2httr2 1.2.2 emits OpenTelemetry traces for every request ⚡
- 11mo agolaterlater 1.4.4 fixes test timings only
- 11mo agolaterlater 1.4.3 stops touching .Random.seed, drops autorun argument
- 1y agohttr2httr2 1.2.1 stops escaping colons in paths
- 1y agohttr2httr2 1.2.0 removes deprecated mocking and streaming APIs
- 1y agohttr2httr2 1.1.2 fixes AWS request signing and header checks
Frequently asked questions
What is the difference between httr2 and later?
Both compete on the same themes — r — within DevOps. httr2 is currently shipping more aggressively (velocity 2.5 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 httr2 better than later?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. httr2 is currently shipping more aggressively (velocity 2.5 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 httr2?
Top httr2 alternatives in DevOps are ranked by recent ship velocity. Browse the "httr2 alternatives" section above for the current picks, or visit /alternatives/httr2 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.