httpuv
httpuv ships almost nothing, which is what you want from the web server under Shiny
A side-by-side editorial comparison of gargle and httr2 — release velocity, themes, recent moves, and the top alternatives to consider.
gargle rebuilt Google auth for R on httr2 and forced the whole wrapper stack to follow
gargle is the shared authentication layer under googledrive, googlesheets4, bigrquery and gmailr, which makes its interface decisions everyone else's migration work. The 1.5.0 release completed the OAuth app-to-client rename and replaced the internal secret handling with exported, httr2-based functions; since then the work has been diagnostics — better retry messaging, escaped error details, and detecting Positron and VS Code alongside RStudio.
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.
gargle is the shared authentication layer under googledrive, googlesheets4, bigrquery and gmailr, which makes its interface decisions everyone else's migration work. The 1.5.0 release completed the OAuth app-to-client rename and replaced the internal secret handling with exported, httr2-based functions; since then the work has been diagnostics — better retry messaging, escaped error details, and detecting Positron and VS Code alongside RStudio.
The package keeps moving toward being debuggable in the environments R actually runs in now: server, Workbench, Colab, VS Code, and non-package projects that still need encrypted credentials. Recent releases export things that used to be internal — last response, last content, error subclasses — which points at wrapper packages needing more control over failure handling than gargle previously allowed.
Expect further exports that let wrapper packages classify and surface Google API errors themselves, and continued detection work as new IDEs and hosted environments appear.
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.
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.
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.
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 gargle or httr2.
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
htmltools spends three releases walking back its own fill-layout opinions
xml2 relicensed to MIT, then moved its hot accessors from S3 into C
httr's last releases are housekeeping - the package now points users at httr2
See all gargle alternatives → · See all httr2 alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — oauth — 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.
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.
Top gargle alternatives in DevOps are ranked by recent ship velocity. Browse the "gargle alternatives" section above for the current picks, or visit /alternatives/gargle for the full list with editorial commentary on each.
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.