httpuv
httpuv ships almost nothing, which is what you want from the web server under Shiny
A side-by-side editorial comparison of later and xml2 — release velocity, themes, recent moves, and the top alternatives to consider.
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.
xml2 relicensed to MIT, then moved its hot accessors from S3 into C
xml2 is the libxml2 binding under most R HTML and XML work, including rvest. Its release cadence is set by libxml2 versions and R CMD check, but two of the last six matter on their own: the 1.3.3 MIT relicense and the 1.3.6 dispatch rewrite that pushed the common accessors into C and dropped three dependencies.
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.
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.
Expect further releases pinned to compiler and Rcpp changes, with the observable surface staying essentially where it is.
xml2 is the libxml2 binding under most R HTML and XML work, including rvest. Its release cadence is set by libxml2 versions and R CMD check, but two of the last six matter on their own: the 1.3.3 MIT relicense and the 1.3.6 dispatch rewrite that pushed the common accessors into C and dropped three dependencies.
This is infrastructure maintenance in the strict sense - most releases exist because the toolchain moved, not because the package did. Where the maintainers do choose the work, it goes to performance and dependency reduction rather than new API, and the surface has been essentially stable since 1.3.0.
Expect the next releases to track libxml2 compatibility and R-devel format-string warnings; new API is unlikely beyond occasional XPath accessors in the style of xml_find_int().
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 later or xml2.
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
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
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. later and xml2 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. later and xml2 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.
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.
Top xml2 alternatives in DevOps are ranked by recent ship velocity. Browse the "xml2 alternatives" section above for the current picks, or visit /alternatives/xml2 for the full list with editorial commentary on each.