clock
clock is turning calendar conventions lubridate hard-coded into parameterized types.
Comparison · DevOps
later vs withr
A side-by-side editorial comparison of later and withr — release velocity, themes, recent moves, and the top alternatives to consider.
later vs withr: at a glance
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.
What is withr?
withr rebuilt defer() on base R's own on.exit(), and got much faster for it
withr provides the with_ and local_ functions that temporarily change global state and restore it on exit - the cleanup primitive under most of the tidyverse test suites. Version 3.0.0 reimplemented defer() as a thin wrapper over base::on.exit(), which the maintainers made possible by contributing the required arguments to R 3.5 itself. Everything since has been small correctness work.
later vs withr: editorial side-by-side
later
0.0DEVOPS
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.
withr
0.0DEVOPS
withr rebuilt defer() on base R's own on.exit(), and got much faster for it
◆ Current state
withr provides the with_ and local_ functions that temporarily change global state and restore it on exit - the cleanup primitive under most of the tidyverse test suites. Version 3.0.0 reimplemented defer() as a thin wrapper over base::on.exit(), which the maintainers made possible by contributing the required arguments to R 3.5 itself. Everything since has been small correctness work.
◆ Where it's heading
The arc here is a package pushing its own machinery down into base R and then living off the result. Once defer() became on.exit(), the remaining work is about where cleanup is allowed to happen - knitr documents, source() calls, the global environment, session end - and about restoring state correctly when an expression exits early. Releases are now infrequent and CRAN-driven.
◆ Prediction
Expect continued low-volume releases fixing edge cases in where deferred handlers run; with the core delegated to base R, there is little left that would prompt a larger change.
Alternatives to later and withr
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 withr.
httpuv
httpuv ships almost nothing, which is what you want from the web server under Shiny
promises
promises drops R6 for plain environments and wires async work into OpenTelemetry
htmltools
htmltools spends three releases walking back its own fill-layout opinions
xml2
xml2 relicensed to MIT, then moved its hot accessors from S3 into C
httr
httr's last releases are housekeeping - the package now points users at httr2
Recent activity from later and withr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agowithrlocal_seed() actually preserves the seed now
- 5mo agolaterlater 1.4.8 tracks Rcpp Rf_error handling changes
- 5mo agolaterlater 1.4.7 fixes a C23 once_flag collision breaking builds
- 6mo agolaterlater 1.4.6 improves idle responsiveness at the R console
- 7mo agolaterlater 1.4.5 drops legacy fallbacks, requires R 3.5 and Rcpp 1.0.10
- 11mo agolaterlater 1.4.4 fixes test timings only
- 11mo agolaterlater 1.4.3 stops touching .Random.seed, drops autorun argument
- 1y agowithrlocal_language() no longer warns when set to C
- 2y agowithrdefer() becomes a thin wrapper over base::on.exit() ⚡
- 4y agowithrCleanup works inside Rmd and source(); with_() gains a getter
- 4y agowithrNew maintainer; handlers run at session end
- 5y agowithrlocal_options() can set NULL; with_seed() controls RNG kind
Frequently asked questions
What is the difference between later and withr?
They serve adjacent needs but don't currently overlap on shipped themes. later and withr 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 withr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. later and withr 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 withr?
Top withr alternatives in DevOps are ranked by recent ship velocity. Browse the "withr alternatives" section above for the current picks, or visit /alternatives/withr for the full list with editorial commentary on each.