clock
clock is turning calendar conventions lubridate hard-coded into parameterized types.
A side-by-side editorial comparison of later and promises — release velocity, themes, recent moves, and the top alternatives to consider.
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.
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.
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.
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.
Expect further releases pinned to compiler and Rcpp changes, with the observable surface staying essentially where it is.
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.
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.
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.
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.
clock is turning calendar conventions lubridate hard-coded into parameterized types.
httpuv ships almost nothing, which is what you want from the web server under Shiny
withr rebuilt defer() on base R's own on.exit(), and got much faster for it
htmltools spends three releases walking back its own fill-layout opinions
xml2 relicensed to MIT, then moved its hot accessors from S3 into C
httr's last releases are housekeeping - the package now points users at httr2
See all later alternatives → · See all promises alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
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.
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.