clock
clock is turning calendar conventions lubridate hard-coded into parameterized types.
A side-by-side editorial comparison of vctrs and withr — release velocity, themes, recent moves, and the top alternatives to consider.
vctrs 0.7 moved conditional recoding down into the tidyverse type system.
vctrs defines the type and size rules underpinning the tidyverse. Its 0.6.x line was pure maintenance — CRAN-requested C changes, R-devel test fixes, ALTREP performance. Version 0.7.0 broke that pattern with a family of conditional and recoding functions that duplicate dplyr verbs at lower cost.
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.
vctrs defines the type and size rules underpinning the tidyverse. Its 0.6.x line was pure maintenance — CRAN-requested C changes, R-devel test fixes, ALTREP performance. Version 0.7.0 broke that pattern with a family of conditional and recoding functions that duplicate dplyr verbs at lower cost.
The package is absorbing operations that previously lived in dplyr, implementing them once against the shared type rules so every consumer inherits consistent semantics. Releases since have tightened attribute handling in vec_restore() and cleared non-API C usage that R's checking tools now flag.
Expect more tidyverse verbs to acquire vctrs-level implementations, and continued removal of non-API C usage as R narrows what packages are permitted to call.
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.
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.
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.
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 vctrs or withr.
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
promises drops R6 for plain environments and wires async work into OpenTelemetry
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
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — performance — within DevOps. vctrs 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. vctrs 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.
Top vctrs alternatives in DevOps are ranked by recent ship velocity. Browse the "vctrs alternatives" section above for the current picks, or visit /alternatives/vctrs for the full list with editorial commentary on each.
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.