← Back to home
Comparison · DevOps

awkward vs purrr

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

awkward vs purrr: at a glance

Featureawkwardpurrr
SectorDevOpsDevOps
Velocity score5.00.0
Sparks · 30d00
Top themesragged arrays, gpu kernels, cuda, numerical stabilitytidyverse, functional-programming, deprecations, parallelism
Last editorial update2h ago1h ago
WebsiteVisit →Visit →

What is awkward?

Awkward Array rewrote its kernels — 5x faster list reductions, and different layouts than before.

Awkward Array releases roughly monthly and has spent the past year rebuilding its compute layer. The CPU kernels were migrated from a parents-based to an offsets-based representation and the GPU kernels moved onto cuda.compute, culminating in 2.10.0's roughly 5x average speedup on list reductions. Since then the work has shifted to numerical robustness — overflow-safe, numerically stable implementations of var, std, mean, covar and corr — and to closing correctness gaps in the Numba lowering path.

Read the full awkward trajectory →

What is purrr?

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.

Read the full purrr trajectory →

awkward vs purrr: editorial side-by-side

A
awkward
DEVOPS
5.0

Awkward Array rewrote its kernels — 5x faster list reductions, and different layouts than before.

◆ Current state

Awkward Array releases roughly monthly and has spent the past year rebuilding its compute layer. The CPU kernels were migrated from a parents-based to an offsets-based representation and the GPU kernels moved onto cuda.compute, culminating in 2.10.0's roughly 5x average speedup on list reductions. Since then the work has shifted to numerical robustness — overflow-safe, numerically stable implementations of var, std, mean, covar and corr — and to closing correctness gaps in the Numba lowering path.

◆ Where it's heading

The project is converging on one kernel specification with CPU and GPU implementations kept in step, so new operations land on both backends in the same release rather than trailing months apart. The willingness to change internal layouts and accept different floating-point results in a minor release says the maintainers treat the kernel layer as private and are optimizing it accordingly. Recurring fixes for silent data corruption in the Numba and cppyy paths suggest the interop surfaces are where the remaining risk sits.

◆ Prediction

Expect the parents-to-offsets migration to finish on the GPU side and the cuda.compute backend to keep absorbing operations that are still CPU-only, with the lazy IR scheduling layer added in 2.11.0 as the next thing to gain visible functionality.

P
purrr
DEVOPS
0.0

purrr finished a decade of deprecations and picked up a parallel backend.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to awkward and purrr

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 awkward or purrr.

See all awkward alternatives → · See all purrr alternatives →

Recent activity from awkward and purrr

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

  1. 14d agoawkward2.12.0: overflow-safe statistics and CUDA argsort
  2. 22d agoawkward2.11.0: a lazy IR scheduling layer and saner parquet row-group defaults
  3. 1mo agoawkward2.10.0: kernels rewritten, list reductions about 5x faster
  4. 2mo agoawkward2.9.1: offsets-based reducers and big-endian support
  5. 4mo agopurrrCRAN check fixes
  6. 6mo agoawkwardVersion 2.9.0
  7. 6mo agoawkward2.8.12: sort, argmax and argmin arrive on the CUDA backend
  8. 7mo agopurrrCompatibility with upcoming vctrs 0.7.0
  9. 9mo agopurrrOld deprecations removed; map_chr() stops coercing
  10. 1y agopurrrin_parallel() adds parallel and distributed maps via mirai
  11. 3y agopurrrValgrind fix and lower map_chr() deprecation overhead
  12. 3y agopurrrIndexed map() errors gain a catchable class and fields

Frequently asked questions

What is the difference between awkward and purrr?

They serve adjacent needs but don't currently overlap on shipped themes. awkward is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is awkward better than purrr?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. awkward is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.

What are the best alternatives to awkward?

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

What are the best alternatives to purrr?

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.