zarr-python
Zarr's package split keeps producing standalone tools: a server, now a lazy indexer.
Comparison · DevOps
callr vs httpuv
A side-by-side editorial comparison of callr and httpuv — release velocity, themes, recent moves, and the top alternatives to consider.
callr vs httpuv: at a glance
What is callr?
callr adds OpenTelemetry tracing, making R subprocess work observable across process boundaries
callr runs R code in fresh subprocesses and had been in maintenance for roughly two years — the 3.7.x releases are error-object polish, DLL handling, and Windows fixes. 3.8.0 breaks that pattern with a batch of substantive changes: pseudo-terminal support, carrier::crate() handling, configurable temp directories, honest non-zero exit statuses, and OpenTelemetry instrumentation.
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.
callr vs httpuv: editorial side-by-side
callr
0.0DEVOPS
callr adds OpenTelemetry tracing, making R subprocess work observable across process boundaries
◆ Current state
callr runs R code in fresh subprocesses and had been in maintenance for roughly two years — the 3.7.x releases are error-object polish, DLL handling, and Windows fixes. 3.8.0 breaks that pattern with a batch of substantive changes: pseudo-terminal support, carrier::crate() handling, configurable temp directories, honest non-zero exit statuses, and OpenTelemetry instrumentation.
◆ Where it's heading
The package is being repositioned from a convenience wrapper into infrastructure that production R workloads can be operated against. Tracing spans that propagate a W3C traceparent into the child process, plus exit codes that finally reflect failure, are both about making callr legible to systems outside R. The pty and libpath changes point the same way — toward callr hosting long-lived, externally managed sessions.
◆ Prediction
Expect the OpenTelemetry surface to spread to sibling packages in the processx/r-lib process stack, and further work on subprocess failure semantics now that non-zero exits are the default.
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 callr 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 callr 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 callr alternatives → · See all httpuv alternatives →
Recent activity from callr and httpuv
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agocallrOpenTelemetry tracing, pty support, and honest subprocess exit codes ⚡
- 1y agohttpuvServes .wasm as application/wasm; mime table refreshed
- 2y agohttpuvrunStaticServer() survives a failed browser launch
- 2y agocallrEnv var to skip copying the client DLL
- 2y agocallrRunning-time fix and fully qualified subprocess calls
- 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
- 3y agocallrErrors carry subprocess stdout and stderr again
- 3y agocallrExperimental add_hook() for subprocess startup
- 4y agocallrUncompressed transport by default; revamped error objects
Frequently asked questions
What is the difference between callr and httpuv?
They serve adjacent needs but don't currently overlap on shipped themes. callr 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 callr better than httpuv?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. callr 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 callr?
Top callr alternatives in DevOps are ranked by recent ship velocity. Browse the "callr alternatives" section above for the current picks, or visit /alternatives/callr 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.