httpuv
httpuv ships almost nothing, which is what you want from the web server under Shiny
A side-by-side editorial comparison of cpp11 and processx — release velocity, themes, recent moves, and the top alternatives to consider.
cpp11 has spent two years rebuilding itself on R's supported API surface
cpp11 is the header-only C++ interface for R packages, and nearly every release in this window is governed by one force: R core's tightening of what counts as non-API. 0.5.0 removed the growable-vector internals that made push_back() cheap, 0.5.3 and 0.5.4 removed further non-API usage, and the small releases in between are crash and compiler-warning fixes.
processx adds kernel-level process pipelines after years of defensive fixes.
processx is the low-level subprocess engine underneath callr and much of the r-lib tooling stack. For several releases it shipped only hardening work: RNG hygiene, safer format strings, signal handling around terminated parents. Version 3.9.0 breaks that pattern with an experimental pipeline class.
cpp11 is the header-only C++ interface for R packages, and nearly every release in this window is governed by one force: R core's tightening of what counts as non-API. 0.5.0 removed the growable-vector internals that made push_back() cheap, 0.5.3 and 0.5.4 removed further non-API usage, and the small releases in between are crash and compiler-warning fixes.
The package is trading a little performance for the right to keep passing CRAN checks indefinitely, and saying so plainly in the release notes. With R >= 4.0 now required, whole compatibility branches have been deleted rather than maintained. The remaining work is narrow: finish the non-API migration, then get back to interface features like cpp_source() handling multiple files.
Expect the last non-API dependencies to be cleared and the deprecated compatibility defines to be removed outright; the entries suggest maintenance discipline rather than new C++ surface.
processx is the low-level subprocess engine underneath callr and much of the r-lib tooling stack. For several releases it shipped only hardening work: RNG hygiene, safer format strings, signal handling around terminated parents. Version 3.9.0 breaks that pattern with an experimental pipeline class.
The package is moving from running one subprocess reliably toward orchestrating graphs of them, with bytes flowing between children through kernel pipes rather than being relayed through R. The new linux_pdeathsig argument points the same way, giving callers real lifecycle control over long-running children.
Expect the pipeline class to lose its experimental label and gain callr integration if the API holds up across both Unix and Windows.
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 cpp11 or processx.
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 cpp11 alternatives → · See all processx alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-lib — within DevOps. cpp11 and processx 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. cpp11 and processx 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 cpp11 alternatives in DevOps are ranked by recent ship velocity. Browse the "cpp11 alternatives" section above for the current picks, or visit /alternatives/cpp11 for the full list with editorial commentary on each.
Top processx alternatives in DevOps are ranked by recent ship velocity. Browse the "processx alternatives" section above for the current picks, or visit /alternatives/processx for the full list with editorial commentary on each.