zarr-python
Zarr's package split keeps producing standalone tools: a server, now a lazy indexer.
Comparison · DevOps
cpp11 vs httpuv
A side-by-side editorial comparison of cpp11 and httpuv — release velocity, themes, recent moves, and the top alternatives to consider.
cpp11 vs httpuv: at a glance
What is cpp11?
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.
What is httpuv?
httpuv ships almost nothing, which is what you want from the web server under Shiny
httpuv is the C++ HTTP and WebSocket server that Shiny runs on. Across this window it added exactly one user-facing function - runStaticServer() for serving a directory - and spent every other release on race conditions, compiler and linker changes, CRAN check warnings, and mime type table updates.
cpp11 vs httpuv: editorial side-by-side
cpp11
0.0DEVOPS
cpp11 has spent two years rebuilding itself on R's supported API surface
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
httpuv
0.0DEVOPS
httpuv ships almost nothing, which is what you want from the web server under Shiny
◆ Current state
httpuv is the C++ HTTP and WebSocket server that Shiny runs on. Across this window it added exactly one user-facing function - runStaticServer() for serving a directory - and spent every other release on race conditions, compiler and linker changes, CRAN check warnings, and mime type table updates.
◆ Where it's heading
There is no direction here in the usual sense, and that is the honest read: the package is a stable foundation whose releases are triggered by the toolchain moving, by R-devel warnings, or by a threading bug surfacing under load. The one recurring theme with substance is connection reliability - WebSocket keepalive pings, race conditions in the I/O thread - which is what actually breaks Shiny apps in production.
◆ Prediction
Expect continued small releases tracking Rtools, R-devel and mime data, with any substantive change most likely coming from a threading or WebSocket issue reported by Shiny users rather than from planned work.
Alternatives to cpp11 and httpuv
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 httpuv.
ellipsis
ellipsis' checks live in rlang now; the package is a compatibility shim.
clock
clock is turning calendar conventions lubridate hard-coded into parameterized types.
promises
promises drops R6 for plain environments and wires async work into OpenTelemetry
withr
withr rebuilt defer() on base R's own on.exit(), and got much faster for it
htmltools
htmltools spends three releases walking back its own fill-layout opinions
See all cpp11 alternatives → · See all httpuv alternatives →
Recent activity from cpp11 and httpuv
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agocpp11cpp_source() accepts multiple files; template crash fixed
- 4mo agocpp11R_NamespaceRegistry usage removed
- 6mo agocpp11ATTRIB() removed; C++ compatibility headers tidied
- 1y agohttpuvServes .wasm as application/wasm; mime table refreshed
- 1y agocpp11cpp11 0.5.2
- 1y agocpp11R 4.0 required; unwind-protect and ALTREP defines retired
- 1y agocpp11Growable-vector internals dropped for R's supported API ⚡
- 2y agohttpuvrunStaticServer() survives a failed browser launch
- 2y agohttpuvRtools build file update and macOS zlib linking fix
- 2y agohttpuvFixes an R CMD check warning on error format strings
- 2y agohttpuvrunStaticServer() serves a directory of static files
- 3y agohttpuvFixes a race condition introduced in 1.6.10
Frequently asked questions
What is the difference between cpp11 and httpuv?
They serve adjacent needs but don't currently overlap on shipped themes. cpp11 and httpuv 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.
Is cpp11 better than httpuv?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. cpp11 and httpuv 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.
What are the best alternatives to cpp11?
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.
What are the best alternatives to httpuv?
Top httpuv alternatives in DevOps are ranked by recent ship velocity. Browse the "httpuv alternatives" section above for the current picks, or visit /alternatives/httpuv for the full list with editorial commentary on each.