← Back to home
Comparison · DevOps

awkward vs withr

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

Shared themes:performance

awkward vs withr: at a glance

Featureawkwardwithr
SectorDevOpsDevOps
Velocity score5.00.0
Sparks · 30d00
Top themesragged arrays, gpu kernels, cuda, numerical stabilitystate-management, testing, performance, base-r
Last editorial update1d 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 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.

Read the full withr trajectory →

awkward vs withr: 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.

W
withr
DEVOPS
0.0

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

See all awkward alternatives → · See all withr alternatives →

Recent activity from awkward and withr

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

  1. 15d agoawkward2.12.0: overflow-safe statistics and CUDA argsort
  2. 23d 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. 1mo agowithrlocal_seed() actually preserves the seed now
  5. 2mo agoawkward2.9.1: offsets-based reducers and big-endian support
  6. 6mo agoawkwardVersion 2.9.0
  7. 6mo agoawkward2.8.12: sort, argmax and argmin arrive on the CUDA backend
  8. 1y agowithrlocal_language() no longer warns when set to C
  9. 2y agowithrdefer() becomes a thin wrapper over base::on.exit()
  10. 4y agowithrCleanup works inside Rmd and source(); with_() gains a getter
  11. 4y agowithrNew maintainer; handlers run at session end
  12. 5y agowithrlocal_options() can set NULL; with_seed() controls RNG kind

Frequently asked questions

What is the difference between awkward and withr?

Both compete on the same themes — performance — within DevOps. 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 withr?

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 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.