← Back to home
Comparison · DevOps

httr2 vs rappdirs

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

httr2 vs rappdirs: at a glance

Featurehttr2rappdirs
SectorDevOpsDevOps
Velocity score2.50.0
Sparks · 30d00
Top themesr, http-client, oauth, opentelemetryfilesystem, config-paths, dependency, dormant
Last editorial update6h ago1h ago
WebsiteVisit →Visit →

What is httr2?

httr2 is growing production concerns: tracing, throttling and token hygiene.

httr2 is the tidyverse's modern HTTP client and the designated successor to httr. Recent releases have moved past request-building ergonomics into operational concerns — OpenTelemetry traces for every request, throttling that behaves correctly across repeated calls, and a fix for OAuth token caches that were never actually being pruned.

Read the full httr2 trajectory →

What is rappdirs?

Load-bearing across CRAN, and untouched since January 2021.

rappdirs answers one question — where does an application put its data, cache and config on this operating system — and it has answered it the same way since 2014. The last release was 0.3.3 in January 2021, a revert of accidental vectorisation introduced four days earlier. The only substantive change in the package's visible history is 0.3.2 teaching user_data_dir(), use_cache_dir() and use_config_dir() to respect the R_USER_DATA_DIR, R_USER_CACHE_DIR and R_USER_CONFIG_DIR environment variables.

Read the full rappdirs trajectory →

httr2 vs rappdirs: editorial side-by-side

H
httr2
DEVOPS
2.5

httr2 is growing production concerns: tracing, throttling and token hygiene.

◆ Current state

httr2 is the tidyverse's modern HTTP client and the designated successor to httr. Recent releases have moved past request-building ergonomics into operational concerns — OpenTelemetry traces for every request, throttling that behaves correctly across repeated calls, and a fix for OAuth token caches that were never actually being pruned.

◆ Where it's heading

The package is maturing into infrastructure for long-running R services rather than interactive scripts. The 1.2.0 lifecycle purge removed deprecated streaming and mocking APIs in favour of a connection-based model, and debugging affordances like httr2_translate() point at users who need to reproduce a failing request outside R.

◆ Prediction

Expect further observability and credential-handling work, with the rlang-driven cache hash change in 1.3.0 likely to surface follow-up issues as existing caches silently invalidate.

R
rappdirs
DEVOPS
0.0

Load-bearing across CRAN, and untouched since January 2021.

◆ Current state

rappdirs answers one question — where does an application put its data, cache and config on this operating system — and it has answered it the same way since 2014. The last release was 0.3.3 in January 2021, a revert of accidental vectorisation introduced four days earlier. The only substantive change in the package's visible history is 0.3.2 teaching user_data_dir(), use_cache_dir() and use_config_dir() to respect the R_USER_DATA_DIR, R_USER_CACHE_DIR and R_USER_CONFIG_DIR environment variables.

◆ Where it's heading

Nothing is heading anywhere, and that is the finding. A port of a Python utility with no open direction, four releases in eleven years, and a dependency position underneath a large share of CRAN packages that need a cache directory. The 0.3.2 and 0.3.3 pair is instructive: a real improvement shipped alongside an accidental behaviour change that had to be reverted within the week, and then silence.

◆ Prediction

The entries give no basis for predicting a next release; on eleven years of evidence the most likely next change is a CRAN-mandated check fix rather than anything user-facing.

Alternatives to httr2 and rappdirs

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 httr2 or rappdirs.

See all httr2 alternatives → · See all rappdirs alternatives →

Recent activity from httr2 and rappdirs

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

  1. 1mo agohttr2httr2 1.3.0 fixes OAuth token caches that never expired
  2. 1mo agohttr2httr2 1.2.3 translates requests into curl commands
  3. 8mo agohttr2httr2 1.2.2 emits OpenTelemetry traces for every request
  4. 1y agohttr2httr2 1.2.1 stops escaping colons in paths
  5. 1y agohttr2httr2 1.2.0 removes deprecated mocking and streaming APIs
  6. 1y agohttr2httr2 1.1.2 fixes AWS request signing and header checks
  7. 5y agorappdirsRevert accidental vectorisation from 0.3.2
  8. 5y agorappdirsRespect the R_USER_*_DIR environment variables
  9. 10y agorappdirsrappdirs 0.3.1
  10. 11y agorappdirsFirst CRAN release

Frequently asked questions

What is the difference between httr2 and rappdirs?

They serve adjacent needs but don't currently overlap on shipped themes. httr2 is currently shipping more aggressively (velocity 2.5 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 httr2 better than rappdirs?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. httr2 is currently shipping more aggressively (velocity 2.5 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 httr2?

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

What are the best alternatives to rappdirs?

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