httpuv
httpuv ships almost nothing, which is what you want from the web server under Shiny
Comparison · DevOps
callr vs vctrs
A side-by-side editorial comparison of callr and vctrs — release velocity, themes, recent moves, and the top alternatives to consider.
callr vs vctrs: 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 vctrs?
vctrs 0.7 moved conditional recoding down into the tidyverse type system.
vctrs defines the type and size rules underpinning the tidyverse. Its 0.6.x line was pure maintenance — CRAN-requested C changes, R-devel test fixes, ALTREP performance. Version 0.7.0 broke that pattern with a family of conditional and recoding functions that duplicate dplyr verbs at lower cost.
callr vs vctrs: 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.
vctrs
0.0DEVOPS
vctrs 0.7 moved conditional recoding down into the tidyverse type system.
◆ Current state
vctrs defines the type and size rules underpinning the tidyverse. Its 0.6.x line was pure maintenance — CRAN-requested C changes, R-devel test fixes, ALTREP performance. Version 0.7.0 broke that pattern with a family of conditional and recoding functions that duplicate dplyr verbs at lower cost.
◆ Where it's heading
The package is absorbing operations that previously lived in dplyr, implementing them once against the shared type rules so every consumer inherits consistent semantics. Releases since have tightened attribute handling in vec_restore() and cleared non-API C usage that R's checking tools now flag.
◆ Prediction
Expect more tidyverse verbs to acquire vctrs-level implementations, and continued removal of non-API C usage as R narrows what packages are permitted to call.
Alternatives to callr and vctrs
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 vctrs.
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
xml2
xml2 relicensed to MIT, then moved its hot accessors from S3 into C
httr
httr's last releases are housekeeping - the package now points users at httr2
Recent activity from callr and vctrs
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agocallrOpenTelemetry tracing, pty support, and honest subprocess exit codes ⚡
- 3mo agovctrsvctrs 0.7.3 removes a non-API PRVALUE() usage
- 4mo agovctrsvctrs 0.7.2 clears unrecognized attributes in vec_restore()
- 6mo agovctrsvctrs 0.7.1 fixes protection issues found by rchk
- 6mo agovctrsvctrs 0.7.0 adds vectorized if-else and case-when ⚡
- 2y agocallrEnv var to skip copying the client DLL
- 2y agocallrRunning-time fix and fully qualified subprocess calls
- 2y agovctrsvctrs 0.6.5 adjusts C format strings for CRAN
- 2y agovctrsvctrs 0.6.4 fixes vec_c() performance with ALTREP vectors
- 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 vctrs?
They serve adjacent needs but don't currently overlap on shipped themes. callr and vctrs 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 vctrs?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. callr and vctrs 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 vctrs?
Top vctrs alternatives in DevOps are ranked by recent ship velocity. Browse the "vctrs alternatives" section above for the current picks, or visit /alternatives/vctrs for the full list with editorial commentary on each.