← Back to home
Comparison · Infra & APIs

carrier vs ggInterval

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

Shared themes:r-package

carrier vs ggInterval: at a glance

FeaturecarrierggInterval
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesr-package, serialization, remote-execution, r-libsymbolic-data-analysis, interval-data, ggplot2, data-visualization
Last editorial update5d ago1h ago
WebsiteVisit →Visit →

What is carrier?

carrier's 0.3.0 quietly rewrites how crated functions see each other — and breaks code that relied on the old rules.

carrier packages an R function together with the data it needs so it can be shipped to another process or machine. 0.3.0 changed the semantics of functions passed through ...: they are now re-crated inside the main crate environment instead of inheriting from wherever they were defined. That fixes helper functions failing to resolve each other remotely, and stops local environments dragging large objects into the payload.

Read the full carrier trajectory →

What is ggInterval?

Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.

ggInterval visualizes symbolic interval-valued data — observations recorded as ranges rather than points — with a family of plot functions in the ggplot2 idiom. The plot catalogue grew most recently with interval correlation heatmaps and interval line plots compatible with time-series input. The three releases before that were corrections: seven plot functions renamed for consistency, examples switched from dontrun to donttest at CRAN's request, and a vignette rewritten to demonstrate every function in one place.

Read the full ggInterval trajectory →

carrier vs ggInterval: editorial side-by-side

C
carrier
INFRA · APIS
0.0

carrier's 0.3.0 quietly rewrites how crated functions see each other — and breaks code that relied on the old rules.

◆ Current state

carrier packages an R function together with the data it needs so it can be shipped to another process or machine. 0.3.0 changed the semantics of functions passed through ...: they are now re-crated inside the main crate environment instead of inheriting from wherever they were defined. That fixes helper functions failing to resolve each other remotely, and stops local environments dragging large objects into the payload.

◆ Where it's heading

Each release tightens the boundary between a crate and its surroundings. 0.2.0 introduced .parent_env defaulting to baseenv() to cut the crate off from the global search path and made unnamed ... arguments an error instead of a silent drop; 0.3.0 finishes the job by controlling the environment chain of the packed closures themselves. The package is trading backwards compatibility for predictable, self-contained payloads — a reasonable bet for something whose failures otherwise surface on a remote worker.

◆ Prediction

The 0.1.0 notes promised an automatic dependency-detection mode to replace explicit packing; nothing since has delivered it, and with the environment semantics now settled that is the obvious next move — though the entries give no date for it.

G
ggInterval
INFRA · APIS
0.0

Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.

◆ Current state

ggInterval visualizes symbolic interval-valued data — observations recorded as ranges rather than points — with a family of plot functions in the ggplot2 idiom. The plot catalogue grew most recently with interval correlation heatmaps and interval line plots compatible with time-series input. The three releases before that were corrections: seven plot functions renamed for consistency, examples switched from dontrun to donttest at CRAN's request, and a vignette rewritten to demonstrate every function in one place.

◆ Where it's heading

The package is consolidating an interface that had drifted. Renaming seven functions in a single release is the clearest signal — the naming was inconsistent enough to be worth breaking, and the vignette rewrite that followed suggests discoverability was the underlying complaint. Underneath that, the additions are steady and narrow: each release brings interval-aware versions of plot types that already exist for point data, which is the whole premise of the package.

◆ Prediction

The pattern of porting one more standard plot type into interval-aware form each release is the most likely continuation; the tsplot compatibility in the latest version hints that time-series interval data is the direction attracting attention.

Alternatives to carrier and ggInterval

Other Infra & APIs 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 carrier or ggInterval.

See all carrier alternatives → · See all ggInterval alternatives →

Recent activity from carrier and ggInterval

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

  1. 3mo agoggIntervalInterval correlation heatmaps and time-series-compatible line plots
  2. 6mo agoggIntervalExamples switched to donttest per CRAN review
  3. 6mo agoggIntervalVignette rewritten to cover every plot function
  4. 6mo agoggIntervalSeven plot functions renamed for consistency
  5. 11mo agocarrierCrated helper functions can now see each other
  6. 1y agocarriercrate() gains .parent_env and stricter argument handling
  7. 3y agocarrierSource references dropped from crated functions
  8. 4y agocarrierInitial release with explicit-only crate packing

Frequently asked questions

What is the difference between carrier and ggInterval?

Both compete on the same themes — r-package — within Infra & APIs. carrier and ggInterval 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 carrier better than ggInterval?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. carrier and ggInterval 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 Infra & APIs products to evaluate alongside.

What are the best alternatives to carrier?

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

What are the best alternatives to ggInterval?

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