stringr
stringr keeps trading convenient guesses for predictable errors.
A side-by-side editorial comparison of purrr and rlang — release velocity, themes, recent moves, and the top alternatives to consider.
purrr finished a decade of deprecations and picked up a parallel backend.
purrr is at 1.2.2, and the last two releases are CRAN check fixes and vctrs compatibility. The substance sits in 1.2.0, which removed everything deprecated back in 0.3.0 and fully deprecated the invoke, lift, cross and splice families soft-deprecated in 1.0.0, while making map_chr() stop silently coercing logicals and numbers to strings. 1.1.0 before it raised the floor to R 4.1 and added in_parallel() on the mirai backend.
rlang moved tidyeval off R's private internals and onto official C API.
rlang is at 1.3.0, which rewrote hash() to walk objects itself rather than lean on R's serialiser — fixing stability against bytecode and shrinkable vectors, at the cost of invalidating every existing hash value. The release before it closed a multi-year effort: rlang and tidyeval are now fully backed by official C APIs of R, work the notes credit to collaboration with R core.
purrr is at 1.2.2, and the last two releases are CRAN check fixes and vctrs compatibility. The substance sits in 1.2.0, which removed everything deprecated back in 0.3.0 and fully deprecated the invoke, lift, cross and splice families soft-deprecated in 1.0.0, while making map_chr() stop silently coercing logicals and numbers to strings. 1.1.0 before it raised the floor to R 4.1 and added in_parallel() on the mirai backend.
The direction is a smaller, stricter surface. Functions that predated the 1.0.0 redesign are being cleared out in stages, and the ones that remain are tightening their type contracts — map_chr() no longer coerces, every() and some() now demand a logical scalar. The parallel work is the one addition, and it arrives as a backend rather than a new way to write maps.
With the 1.0.0 soft deprecations now fully deprecated and marked for removal, the next release most likely deletes them rather than adding capability.
rlang is at 1.3.0, which rewrote hash() to walk objects itself rather than lean on R's serialiser — fixing stability against bytecode and shrinkable vectors, at the cost of invalidating every existing hash value. The release before it closed a multi-year effort: rlang and tidyeval are now fully backed by official C APIs of R, work the notes credit to collaboration with R core.
The through-line across this whole window is one migration. Release after release retires something that depended on private R internals — env_browse(), env_unlock(), ns_registry_env(), the SEXP iterator now behind a compile flag — and replaces it with sanctioned API. The hash() rewrite in 1.3.0 is the same instinct applied to the serialiser: own the behaviour rather than inherit it.
With the C API migration declared complete in 1.2.0, the next releases are likely to be ordinary maintenance and type-checking additions rather than further defunct markings.
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 purrr or rlang.
stringr keeps trading convenient guesses for predictable errors.
pyjanitor is folding its verbs into pandas groupby objects, one release at a time.
PyTables opened a path around HDF5's filter pipeline, then chased Python's runtime.
R's API framework grew its serializer catalogue, then went quiet on features.
Dask's scheduler spent the year deleting deprecated API, not adding surface.
The HEIF library quietly became a video decoder, then a scientific image container.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — tidyverse, r-language — within DevOps. purrr and rlang 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. purrr and rlang 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 purrr alternatives in DevOps are ranked by recent ship velocity. Browse the "purrr alternatives" section above for the current picks, or visit /alternatives/purrr for the full list with editorial commentary on each.
Top rlang alternatives in DevOps are ranked by recent ship velocity. Browse the "rlang alternatives" section above for the current picks, or visit /alternatives/rlang for the full list with editorial commentary on each.