httpuv
httpuv ships almost nothing, which is what you want from the web server under Shiny
A side-by-side editorial comparison of Fiber and gargle — release velocity, themes, recent moves, and the top alternatives to consider.
Fiber v3 has sat in release candidate for months while v2 gets one-line patches
The feed carries two lines that barely touch. Fiber v2 receives narrow maintenance releases — a lock cleanup, an X-Real-IP backport, an HTML escaping fix, a CVE patch — most containing a single merged PR. The v3 line, last visible here at rc.3, is where the actual work is: native net/http and fasthttp handler support, Express-style request and response handlers, HostClient and LBClient in the client package.
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.
The feed carries two lines that barely touch. Fiber v2 receives narrow maintenance releases — a lock cleanup, an X-Real-IP backport, an HTML escaping fix, a CVE patch — most containing a single merged PR. The v3 line, last visible here at rc.3, is where the actual work is: native net/http and fasthttp handler support, Express-style request and response handlers, HostClient and LBClient in the client package.
v3 is the answer to Fiber's longest-standing objection, that building on fasthttp cuts a project off from the net/http middleware ecosystem. Making both handler styles native reframes Fiber as compatible rather than separate. But rc.3 dates to late 2025 and nothing newer has landed in this feed, while v2 patches keep arriving through August — a long release candidate stretch that leaves users choosing between a stable branch in pure maintenance and a v3 that has not been declared final.
The next meaningful entry is either a v3.0.0 final or a further RC; until one lands, expect the v2 line to continue receiving single-PR backports and security patches.
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.
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 Fiber or gargle.
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 Fiber alternatives → · See all gargle alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Fiber 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. Fiber 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 Fiber alternatives in DevOps are ranked by recent ship velocity. Browse the "Fiber alternatives" section above for the current picks, or visit /alternatives/fiber for the full list with editorial commentary on each.
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.