← Back to home
Comparison · DevOps

callr vs ellipsis

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

callr vs ellipsis: at a glance

Featurecallrellipsis
SectorDevOpsDevOps
Velocity score0.00.0
Sparks · 30d00
Top themessubprocess, observability, opentelemetry, r-libargument checking, rlang, tidyverse, superseded package
Last editorial update2h ago50m 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 ellipsis?

ellipsis' checks live in rlang now; the package is a compatibility shim.

ellipsis provides check_dots_used(), check_dots_unnamed() and check_dots_empty() for catching arguments silently swallowed by dots. Its functional development finished in 2019 across the 0.2.0 and 0.3.0 releases. The two releases since deal only with rlang and CRAN, and 0.3.3 makes the rlang dependency unconditional.

Read the full ellipsis trajectory →

callr vs ellipsis: 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.

E
ellipsis
DEVOPS
0.0

ellipsis' checks live in rlang now; the package is a compatibility shim.

◆ Current state

ellipsis provides check_dots_used(), check_dots_unnamed() and check_dots_empty() for catching arguments silently swallowed by dots. Its functional development finished in 2019 across the 0.2.0 and 0.3.0 releases. The two releases since deal only with rlang and CRAN, and 0.3.3 makes the rlang dependency unconditional.

◆ Where it's heading

The package built its full surface quickly, hardened it once by switching the check functions from warnings to errors, then saw the ideas move upstream. These checks are part of rlang's own API now, which leaves ellipsis as a compatibility layer for packages still importing it directly. The 0.3.3 change to depend on rlang unconditionally states that relationship plainly.

◆ Prediction

With the functionality living in rlang, the next release is most likely another CRAN-driven fix; there is no sign of new checks being added here.

Alternatives to callr and ellipsis

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

See all callr alternatives → · See all ellipsis alternatives →

Recent activity from callr and ellipsis

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

  1. 2mo agocallrOpenTelemetry tracing, pty support, and honest subprocess exit codes
  2. 4mo agoellipsisNow depends unconditionally on rlang
  3. 2y agocallrEnv var to skip copying the client DLL
  4. 2y agocallrRunning-time fix and fully qualified subprocess calls
  5. 3y agocallrErrors carry subprocess stdout and stderr again
  6. 3y agocallrExperimental add_hook() for subprocess startup
  7. 4y agocallrUncompressed transport by default; revamped error objects
  8. 5y agoellipsisLicense changed to MIT; rlang compatibility updated
  9. 6y agoellipsisR-devel fix and new ?dots_used documentation topic
  10. 6y agoellipsischeck_dots_* functions gain an action argument
  11. 7y agoellipsischeck_ functions now throw errors; check_dots_empty() added
  12. 7y agoellipsischeck_dots_unnamed() added

Frequently asked questions

What is the difference between callr and ellipsis?

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

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

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