← Back to home
Comparison · Infra & APIs

carrier vs eratosthenes

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

Shared themes:r-package

carrier vs eratosthenes: at a glance

Featurecarriereratosthenes
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themesr-package, serialization, remote-execution, r-libarchaeology, bayesian-inference, mcmc, input-validation
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 eratosthenes?

eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.

eratosthenes does Bayesian estimation of archaeological chronologies from relative sequences, absolute constraints and artifact assemblages. The 0.0.9 line built out the inference diagnostics — traceplots, histograms, batch-means MCSE reporting, displacement estimation — and then consolidated artifact probability-density estimation into a single gibbs_ad_type(). The 0.1.0 tag turns outward instead, adding validators for every user-supplied structure and replacing seq_check() with a more informative seq_diag().

Read the full eratosthenes trajectory →

carrier vs eratosthenes: 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.

E
eratosthenes
INFRA · APIS
2.5

eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.

◆ Current state

eratosthenes does Bayesian estimation of archaeological chronologies from relative sequences, absolute constraints and artifact assemblages. The 0.0.9 line built out the inference diagnostics — traceplots, histograms, batch-means MCSE reporting, displacement estimation — and then consolidated artifact probability-density estimation into a single gibbs_ad_type(). The 0.1.0 tag turns outward instead, adding validators for every user-supplied structure and replacing seq_check() with a more informative seq_diag().

◆ Where it's heading

The package is moving from research code to something a non-author can run. Consolidating estimation behind one function, then wrapping every input class in a validator, are the two steps that make failures legible instead of cryptic, and the diagnostics added earlier serve the same end for the sampler itself. Nothing in the window changes the underlying model; the work is all about making it usable and its output checkable.

◆ Prediction

With inputs validated and diagnostics in place, the next release is more likely to extend the constraint or assemblage modelling than to keep reworking the interface, though the feed's three sparse tags give little to read a cadence from.

Alternatives to carrier and eratosthenes

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

See all carrier alternatives → · See all eratosthenes alternatives →

Recent activity from carrier and eratosthenes

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

  1. 10d agoeratosthenesInput validators added; seq_check() replaced by seq_diag()
  2. 11mo agocarrierCrated helper functions can now see each other
  3. 1y agoeratosthenesArtifact p.d.f. estimation consolidated into gibbs_ad_type()
  4. 1y agoeratosthenesMCMC diagnostics arrive: traceplots, histograms, batch-means MCSE
  5. 1y agocarriercrate() gains .parent_env and stricter argument handling
  6. 3y agocarrierSource references dropped from crated functions
  7. 4y agocarrierInitial release with explicit-only crate packing

Frequently asked questions

What is the difference between carrier and eratosthenes?

Both compete on the same themes — r-package — within Infra & APIs. eratosthenes is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is carrier better than eratosthenes?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. eratosthenes is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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 eratosthenes?

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