zarr-python
Zarr's package split keeps producing standalone tools: a server, now a lazy indexer.
Comparison · DevOps
callr vs xml2
A side-by-side editorial comparison of callr and xml2 — release velocity, themes, recent moves, and the top alternatives to consider.
callr vs xml2: 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 xml2?
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.
callr vs xml2: 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.
xml2
0.0DEVOPS
xml2 relicensed to MIT, then moved its hot accessors from S3 into C
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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().
Alternatives to callr and xml2
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 xml2.
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.
httpuv
httpuv ships almost nothing, which is what you want from the web server under Shiny
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
Recent activity from callr and xml2
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agocallrOpenTelemetry tracing, pty support, and honest subprocess exit codes ⚡
- 2y agocallrEnv var to skip copying the client DLL
- 2y agocallrRunning-time fix and fully qualified subprocess calls
- 2y agoxml2Accessors dispatch in C; glue, withr and lifecycle dropped
- 3y agoxml2Small xml_find_all() speedup and check fixes
- 3y agoxml2R CMD check fixes and a Windows libxml2 bump
- 3y agocallrErrors carry subprocess stdout and stderr again
- 3y agocallrExperimental add_hook() for subprocess startup
- 4y agocallrUncompressed transport by default; revamped error objects
- 4y agoxml2Relicensed to MIT, with Hadley Wickham back as maintainer ⚡
- 6y agoxml2Rejects multi-element strings; fixes a raw-input regression
- 6y agoxml2Restores reading HTML with non-ASCII encodings
Frequently asked questions
What is the difference between callr and xml2?
They serve adjacent needs but don't currently overlap on shipped themes. callr 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.
Is callr better than xml2?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. callr 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.
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 xml2?
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.