← Back to home
Comparison · Infra & APIs

carrier vs nuggets

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

Shared themes:r-package

carrier vs nuggets: at a glance

Featurecarriernuggets
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themesr-package, serialization, remote-execution, r-libpattern-mining, association-rules, guha, cpp-performance
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 nuggets?

nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.

nuggets searches for association rules, contrasts and other conditional patterns in the GUHA tradition, with a C++ core behind dig() and an interactive explore() app for reading results. Since the 2.0 rewrite of that core, every release has widened the same three surfaces: more pattern families to mine, more of explore() to inspect them in, and steady performance work underneath. The most recent tag optimises dig() on sparse crisp data with a sparse bit chain and adds clustering characteristics to explore() for association rules.

Read the full nuggets trajectory →

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

N
nuggets
INFRA · APIS
2.5

nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.

◆ Current state

nuggets searches for association rules, contrasts and other conditional patterns in the GUHA tradition, with a C++ core behind dig() and an interactive explore() app for reading results. Since the 2.0 rewrite of that core, every release has widened the same three surfaces: more pattern families to mine, more of explore() to inspect them in, and steady performance work underneath. The most recent tag optimises dig() on sparse crisp data with a sparse bit chain and adds clustering characteristics to explore() for association rules.

◆ Where it's heading

Two forces are shaping the package. One is coverage: baseline, complement and paired-baseline contrasts, correlations, tautologies, ancestors and clustering have all been added as first-class dig_ or explore_ surfaces, so the same search engine now answers a widening set of questions. The other is weight — Shiny packages moved from Imports to Suggests, BH and RcppThread dropped, XSIMD updated, parse_condition() rewritten in C++ — which keeps a package with an interactive app from forcing that app's dependencies on every user. Deprecations are handled through lifecycle rather than removed abruptly.

◆ Prediction

Expect the sparse-data optimisation to extend from crisp to fuzzy data, and explore() to keep gaining tabs as each new pattern family lands, on the roughly six-week cadence the 2.2 line has held.

Alternatives to carrier and nuggets

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

See all carrier alternatives → · See all nuggets alternatives →

Recent activity from carrier and nuggets

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

  1. 27d agonuggetsSparse bit chain speeds dig(); explore() gains clustering
  2. 2mo agonuggetspartition() gains .subsets; geom_diamond() layout improved
  3. 5mo agonuggetsexplore() covers contrasts and correlations; dig_ancestors() added
  4. 6mo agonuggetsCritical explore() bug fixed; is_logicalish() added
  5. 6mo agonuggetsShiny deps moved to Suggests; BH and RcppThread dropped
  6. 8mo agonuggetscluster_associations() and add_interest() arrive; C++ condition parser
  7. 11mo agocarrierCrated helper functions can now see each other
  8. 1y agocarriercrate() gains .parent_env and stricter argument handling
  9. 3y agocarrierSource references dropped from crated functions
  10. 4y agocarrierInitial release with explicit-only crate packing

Frequently asked questions

What is the difference between carrier and nuggets?

Both compete on the same themes — r-package — within Infra & APIs. nuggets 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 nuggets?

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

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