← Back to home
Comparison · DevOps

later vs promises

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

Shared themes:async

later vs promises: at a glance

Featurelaterpromises
SectorDevOpsDevOps
Velocity score0.00.0
Sparks · 30d00
Top themesr, event-loop, async, rcppasync, observability, performance, shiny
Last editorial update2h ago59m ago
WebsiteVisit →Visit →

What is later?

later spends its releases keeping R's event loop compiling against moving toolchains.

later provides the event loop that lets R schedule callbacks, underpinning shiny, httpuv and most async work in the language. Recent releases are overwhelmingly build and compatibility work: Rcpp error-handling changes, a C23 namespace collision with glibc, and header ordering to satisfy Rcpp auto-includes.

Read the full later trajectory →

What is promises?

promises drops R6 for plain environments and wires async work into OpenTelemetry

promises supplies the async primitives behind Shiny and plumber. After years of small domain and future() fixes, the last two releases changed both what a promise costs and what it can report: 1.4.0 corrected nested domain ordering and added the first OpenTelemetry integration, and 1.5.0 replaced the R6 promise class with a classed environment while stabilizing the tracing API.

Read the full promises trajectory →

later vs promises: editorial side-by-side

L
later
DEVOPS
0.0

later spends its releases keeping R's event loop compiling against moving toolchains.

◆ Current state

later provides the event loop that lets R schedule callbacks, underpinning shiny, httpuv and most async work in the language. Recent releases are overwhelmingly build and compatibility work: Rcpp error-handling changes, a C23 namespace collision with glibc, and header ordering to satisfy Rcpp auto-includes.

◆ Where it's heading

The API is settled enough that the release calendar is set by the surrounding ecosystem rather than by any feature plan. 1.4.5 cleaned house by dropping pre-unwind-protect fallbacks, and 1.4.6 carries the only recent change a user would notice at all — lower CPU use when idle at the console.

◆ Prediction

Expect further releases pinned to compiler and Rcpp changes, with the observable surface staying essentially where it is.

P
promises
DEVOPS
0.0

promises drops R6 for plain environments and wires async work into OpenTelemetry

◆ Current state

promises supplies the async primitives behind Shiny and plumber. After years of small domain and future() fixes, the last two releases changed both what a promise costs and what it can report: 1.4.0 corrected nested domain ordering and added the first OpenTelemetry integration, and 1.5.0 replaced the R6 promise class with a classed environment while stabilizing the tracing API.

◆ Where it's heading

Two things are being fixed at once. Promise domains - the mechanism that carries context across async boundaries - have been the source of nearly every bug in this window, and they are now being used deliberately as the vehicle for tracing rather than just for error handling. Meanwhile the object itself is being made cheap enough to create in volume.

◆ Prediction

Expect the OpenTelemetry surface to lose its experimental label and pick up the same span coverage Shiny would need end to end; the deprecated ospan function names should be removed in a following release.

Alternatives to later and promises

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 later or promises.

See all later alternatives → · See all promises alternatives →

Recent activity from later and promises

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

  1. 5mo agolaterlater 1.4.8 tracks Rcpp Rf_error handling changes
  2. 5mo agolaterlater 1.4.7 fixes a C23 once_flag collision breaking builds
  3. 6mo agolaterlater 1.4.6 improves idle responsiveness at the R console
  4. 7mo agolaterlater 1.4.5 drops legacy fallbacks, requires R 3.5 and Rcpp 1.0.10
  5. 9mo agopromisesOpenTelemetry spans across async work; R6 dropped for environments
  6. 9mo agopromisesNested promise domains fixed; then() gains a tee argument
  7. 11mo agolaterlater 1.4.4 fixes test timings only
  8. 11mo agolaterlater 1.4.3 stops touching .Random.seed, drops autorun argument
  9. 1y agopromisesRealigns future object creation with the future package
  10. 1y agopromisesFixes stack overflow on long promise chains
  11. 1y agopromisesFixes domains forgotten inside nested handlers
  12. 3y agopromisesfuture_promise() returns early when workers are exhausted

Frequently asked questions

What is the difference between later and promises?

Both compete on the same themes — async — within DevOps. later and promises 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 later better than promises?

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

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

What are the best alternatives to promises?

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