← Back to home
Comparison · Infra & APIs

carrier vs q2

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

carrier vs q2: at a glance

Featurecarrierq2
SectorInfra & APIsInfra & APIs
Velocity score0.06.3
Sparks · 30d01
Top themesr-package, serialization, remote-execution, r-librust-rewrite, publishing-toolchain, quarto, developer-tooling
Last editorial update2h 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 q2?

Ten releases in six days, methodically porting Quarto's surface into a Rust binary.

q2 is the Quarto team's Rust reimplementation of Quarto, shipping as a statically linked single binary with signed release archives and a bundled Quarto Hub MCP server. It is explicitly marked experimental and not production-ready, and it is moving fast — ten releases between 7 and 13 August. The release notes are raw commit logs rather than curated summaries, and reading them shows a consistent programme: work items are investigated, design decisions recorded, tests written red, then implemented in numbered phases, with 'Q1 parity' as the recurring benchmark against the existing Quarto.

Read the full q2 trajectory →

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

Q
q2
INFRA · APIS
6.3

Ten releases in six days, methodically porting Quarto's surface into a Rust binary.

◆ Current state

q2 is the Quarto team's Rust reimplementation of Quarto, shipping as a statically linked single binary with signed release archives and a bundled Quarto Hub MCP server. It is explicitly marked experimental and not production-ready, and it is moving fast — ten releases between 7 and 13 August. The release notes are raw commit logs rather than curated summaries, and reading them shows a consistent programme: work items are investigated, design decisions recorded, tests written red, then implemented in numbered phases, with 'Q1 parity' as the recurring benchmark against the existing Quarto.

◆ Where it's heading

The project is working through the original Quarto's feature surface item by item — project profiles, environment files, shortcodes in metadata, listings, callouts, crossrefs, TOC handling, aliases — while building infrastructure the original lacks, notably a numbered diagnostic catalogue (Q-2-47, Q-14-4 and so on) with a lint that requires a documentation page for every error code. Version 0.18.0's Lua filter support is the load-bearing one, since Quarto's extension ecosystem is written in Lua. Distribution choices point at the same goal: musl-static Linux builds, minisign signatures, no glibc requirement.

◆ Prediction

Expect the parity grind to continue at this cadence, with the remaining high-value Q1 features and diagnostic coverage as the visible queue. The commit logs also show npx distribution planned for the MCP server, which is the nearest thing to a stated roadmap item in these entries.

Alternatives to carrier and q2

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

See all carrier alternatives → · See all q2 alternatives →

Recent activity from carrier and q2

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

  1. 17h agoq2TOC entries carry inline markup; draft banner restored
  2. 1d agoq2Adds alias redirect stubs and diagnostic suppression
  3. 2d agoq2Bumps samod and automerge; fixes indented continuations
  4. 2d agoq2Lua filters supported; mermaid bundled instead of CDN-loaded
  5. 3d agoq2Mermaid cell options, callout titles, email autolinks
  6. 3d agoq2Project profiles, environment files, shortcodes in metadata
  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 q2?

They serve adjacent needs but don't currently overlap on shipped themes. q2 is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 q2?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. q2 is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 q2?

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