← Back to home
Comparison · DevOps

callr vs withr

A side-by-side editorial comparison of callr and withr — release velocity, themes, recent moves, and the top alternatives to consider.

callr vs withr: at a glance

Featurecallrwithr
SectorDevOpsDevOps
Velocity score0.00.0
Sparks · 30d00
Top themessubprocess, observability, opentelemetry, r-libstate-management, testing, performance, base-r
Last editorial update2h ago1h ago
WebsiteVisit →Visit →

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.

Read the full callr trajectory →

What is withr?

withr rebuilt defer() on base R's own on.exit(), and got much faster for it

withr provides the with_ and local_ functions that temporarily change global state and restore it on exit - the cleanup primitive under most of the tidyverse test suites. Version 3.0.0 reimplemented defer() as a thin wrapper over base::on.exit(), which the maintainers made possible by contributing the required arguments to R 3.5 itself. Everything since has been small correctness work.

Read the full withr trajectory →

callr vs withr: editorial side-by-side

C
callr
DEVOPS
0.0

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.

W
withr
DEVOPS
0.0

withr rebuilt defer() on base R's own on.exit(), and got much faster for it

◆ Current state

withr provides the with_ and local_ functions that temporarily change global state and restore it on exit - the cleanup primitive under most of the tidyverse test suites. Version 3.0.0 reimplemented defer() as a thin wrapper over base::on.exit(), which the maintainers made possible by contributing the required arguments to R 3.5 itself. Everything since has been small correctness work.

◆ Where it's heading

The arc here is a package pushing its own machinery down into base R and then living off the result. Once defer() became on.exit(), the remaining work is about where cleanup is allowed to happen - knitr documents, source() calls, the global environment, session end - and about restoring state correctly when an expression exits early. Releases are now infrequent and CRAN-driven.

◆ Prediction

Expect continued low-volume releases fixing edge cases in where deferred handlers run; with the core delegated to base R, there is little left that would prompt a larger change.

Alternatives to callr and withr

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 withr.

See all callr alternatives → · See all withr alternatives →

Recent activity from callr and withr

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1mo agowithrlocal_seed() actually preserves the seed now
  2. 2mo agocallrOpenTelemetry tracing, pty support, and honest subprocess exit codes
  3. 1y agowithrlocal_language() no longer warns when set to C
  4. 2y agocallrEnv var to skip copying the client DLL
  5. 2y agocallrRunning-time fix and fully qualified subprocess calls
  6. 2y agowithrdefer() becomes a thin wrapper over base::on.exit()
  7. 3y agocallrErrors carry subprocess stdout and stderr again
  8. 3y agocallrExperimental add_hook() for subprocess startup
  9. 4y agocallrUncompressed transport by default; revamped error objects
  10. 4y agowithrCleanup works inside Rmd and source(); with_() gains a getter
  11. 4y agowithrNew maintainer; handlers run at session end
  12. 5y agowithrlocal_options() can set NULL; with_seed() controls RNG kind

Frequently asked questions

What is the difference between callr and withr?

They serve adjacent needs but don't currently overlap on shipped themes. callr and withr 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 withr?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. callr and withr 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 withr?

Top withr alternatives in DevOps are ranked by recent ship velocity. Browse the "withr alternatives" section above for the current picks, or visit /alternatives/withr for the full list with editorial commentary on each.