httpuv
httpuv ships almost nothing, which is what you want from the web server under Shiny
A side-by-side editorial comparison of ASP.NET Core and withr — release velocity, themes, recent moves, and the top alternatives to consider.
ASP.NET Core's public feed is servicing traffic; the real work happens on the .NET 11 previews.
The repository ships on a predictable servicing rhythm — monthly patch rollups across the 8.0, 9.0, and 10.0 branches, dominated by branding bumps, dependency updates, and build-infrastructure work. User-visible changes are rare and concentrated in the 10.0 line, where Blazor fixes still land. The 11.0 preview tags appear separately and carry single commits rather than release notes.
withr rebuilt defer() on base R's own on.exit(), and got much faster for it
withr provides the with_ and local_ functions that temporarily change global state and restore it on exit - the cleanup primitive under most of the tidyverse test suites. Version 3.0.0 reimplemented defer() as a thin wrapper over base::on.exit(), which the maintainers made possible by contributing the required arguments to R 3.5 itself. Everything since has been small correctness work.
The repository ships on a predictable servicing rhythm — monthly patch rollups across the 8.0, 9.0, and 10.0 branches, dominated by branding bumps, dependency updates, and build-infrastructure work. User-visible changes are rare and concentrated in the 10.0 line, where Blazor fixes still land. The 11.0 preview tags appear separately and carry single commits rather than release notes.
Nothing in this feed suggests a directional shift: the 8.0 and 9.0 branches are in maintenance, 10.0 absorbs the remaining behavioral fixes, and 11.0 is accumulating previews one commit at a time. Recent servicing entries lean unusually heavily toward CI and internal feed authentication work — the team replacing expired PATs with build identity and moving pipelines to newer images. Read this feed for stability signals, not for product direction.
The cadence points to continued monthly servicing across all three branches, with .NET 11 preview tags accumulating until a preview release note consolidates them into something readable.
withr provides the with_ and local_ functions that temporarily change global state and restore it on exit - the cleanup primitive under most of the tidyverse test suites. Version 3.0.0 reimplemented defer() as a thin wrapper over base::on.exit(), which the maintainers made possible by contributing the required arguments to R 3.5 itself. Everything since has been small correctness work.
The arc here is a package pushing its own machinery down into base R and then living off the result. Once defer() became on.exit(), the remaining work is about where cleanup is allowed to happen - knitr documents, source() calls, the global environment, session end - and about restoring state correctly when an expression exits early. Releases are now infrequent and CRAN-driven.
Expect continued low-volume releases fixing edge cases in where deferred handlers run; with the core delegated to base R, there is little left that would prompt a larger change.
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 ASP.NET Core or withr.
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
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
magrittr rewrote its pipe in C, then base R shipped one and the releases stopped
See all ASP.NET Core alternatives → · See all withr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — maintenance — within DevOps. ASP.NET Core 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ASP.NET Core 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.
Top ASP.NET Core alternatives in DevOps are ranked by recent ship velocity. Browse the "ASP.NET Core alternatives" section above for the current picks, or visit /alternatives/aspnet-core for the full list with editorial commentary on each.
Top withr alternatives in DevOps are ranked by recent ship velocity. Browse the "withr alternatives" section above for the current picks, or visit /alternatives/withr for the full list with editorial commentary on each.