← Back to home
Comparison · Infra & APIs

rstudio.prefs vs usmapdata

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

Shared themes:r-packages

rstudio.prefs vs usmapdata: at a glance

Featurerstudio.prefsusmapdata
SectorInfra & APIsInfra & APIs
Velocity score2.52.5
Sparks · 30d00
Top themesr-packages, rstudio, developer-tools, configuration-as-coder-packages, geospatial, census-data, cartography
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is rstudio.prefs?

Four years dormant, rstudio.prefs returns under a new maintainer.

The package scripts RStudio's own settings — preferences, secondary repositories, keyboard shortcuts — as code you can drop into a project or an onboarding doc. After 0.1.9 in July 2022 it went quiet for four years. 0.2.0 ends that with a maintainer handoff from Daniel D. Sjoberg to S.A. van der Wulp, a shortcut-removal path, and a fix for a corrupted addins.json entry that made reassigned shortcuts fail silently.

Read the full rstudio.prefs trajectory →

What is usmapdata?

usmapdata ships its 2025 shapefiles on the year-indexed model it adopted in 0.4.0.

usmapdata supplies the boundary data behind usmap's plotting functions. Since 0.4.0 it has been year-indexed: us_map(data_year = ) selects a vintage, and each Census release is added as its own year with older ones still reachable. 1.1.0 adds 2025. 1.0.0 closed the package's longest-standing gap by adding Puerto Rico, retroactively across every vintage.

Read the full usmapdata trajectory →

rstudio.prefs vs usmapdata: editorial side-by-side

R
rstudio.prefs
INFRA · APIS
2.5

Four years dormant, rstudio.prefs returns under a new maintainer.

◆ Current state

The package scripts RStudio's own settings — preferences, secondary repositories, keyboard shortcuts — as code you can drop into a project or an onboarding doc. After 0.1.9 in July 2022 it went quiet for four years. 0.2.0 ends that with a maintainer handoff from Daniel D. Sjoberg to S.A. van der Wulp, a shortcut-removal path, and a fix for a corrupted addins.json entry that made reassigned shortcuts fail silently.

◆ Where it's heading

The through-line is teaching every setter how to unset. Secondary repositories got NULL removal back in 0.1.6; 0.2.0 extends the same convention to keyboard shortcuts. Most of the rest of 0.2.0 is arrears — a stale documentation URL that hid preferences such as enable_splash_screen, a deprecated purrr::update_list() call, and check_shortcut_consistency() erroring early on an unknown name.

◆ Prediction

With a new maintainer and refreshed GitHub Actions, the near-term work is likely more catch-up of the same kind: remaining deprecated dependencies and the preference list that fetch_rstudio_prefs() reads from RStudio's docs. Nothing in these notes points past RStudio settings as the scope.

U
usmapdata
INFRA · APIS
2.5

usmapdata ships its 2025 shapefiles on the year-indexed model it adopted in 0.4.0.

◆ Current state

usmapdata supplies the boundary data behind usmap's plotting functions. Since 0.4.0 it has been year-indexed: us_map(data_year = ) selects a vintage, and each Census release is added as its own year with older ones still reachable. 1.1.0 adds 2025. 1.0.0 closed the package's longest-standing gap by adding Puerto Rico, retroactively across every vintage.

◆ Where it's heading

The package has settled into a predictable rhythm — one shapefile vintage per year, with structural change rare and clustered. The two changes that mattered were data_year in 0.4.0, which turned a single-vintage dataset into a time series, and the tibble-to-data-frame switch in 0.6.0 that reduced what downstream callers have to depend on.

◆ Prediction

The stated policy — each year added going forward, previous years reachable through data_year — points to a 2026 vintage as the next release. Nothing in these notes suggests further change to the data model.

Alternatives to rstudio.prefs and usmapdata

Other Infra & APIs 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 rstudio.prefs or usmapdata.

See all rstudio.prefs alternatives → · See all usmapdata alternatives →

Recent activity from rstudio.prefs and usmapdata

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

  1. 7h agorstudio.prefsShortcut removal, an addins.json fix, and a new maintainer
  2. 23d agousmapdata2025 Census shapefiles added
  3. 0y agousmapdataPuerto Rico added across every map vintage
  4. 1y agousmapdataus_map() returns a data frame instead of a tibble
  5. 1y agousmapdata2024 Census shapefiles added
  6. 1y agousmapdatadata_year turns the package into a multi-vintage archive
  7. 2y agousmapdataMap data moves to 2023 shapefiles
  8. 4y agorstudio.prefsPreferences now read and written through rstudioapi
  9. 4y agorstudio.prefsConfig files left alone when nothing would change
  10. 4y agorstudio.prefsSecondary repositories can be deleted again
  11. 4y agorstudio.prefsRepository removal via NULL; config path helpers exported
  12. 5y agorstudio.prefsDocumentation, error messages, and array-type caution

Frequently asked questions

What is the difference between rstudio.prefs and usmapdata?

Both compete on the same themes — r-packages — within Infra & APIs. rstudio.prefs and usmapdata are shipping at a similar cadence (velocity 2.5 vs 2.5, 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.

Is rstudio.prefs better than usmapdata?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rstudio.prefs and usmapdata are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to rstudio.prefs?

Top rstudio.prefs alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rstudio.prefs alternatives" section above for the current picks, or visit /alternatives/rstudio-prefs for the full list with editorial commentary on each.

What are the best alternatives to usmapdata?

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