← Back to home
Comparison · Infra & APIs

inlabru vs rstudio.prefs

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

inlabru vs rstudio.prefs: at a glance

Featureinlabrurstudio.prefs
SectorInfra & APIsInfra & APIs
Velocity score2.52.5
Sparks · 30d00
Top themesbayesian-modelling, spatial-statistics, r-package, api-consolidationr-packages, rstudio, developer-tools, configuration-as-code
Last editorial update2h ago1h ago
WebsiteVisit →Visit →

What is inlabru?

A Bayesian spatial modelling package rebuilding its foundations one breaking release at a time

inlabru wraps INLA for spatial, point-process and latent-Gaussian models in R. It is mid-modernisation: since 2.12.0 cut the sp stack, each release has renamed part of the public surface, standardised how external packages attach custom mappers, or replaced internal machinery. 2.15.0 is the latest step, pairing a new predictor evaluation and linearisation implementation with broom's tidy(), glance() and augment() methods and four non-zero-truncated observation families.

Read the full inlabru trajectory →

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 →

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

I
inlabru
INFRA · APIS
2.5

A Bayesian spatial modelling package rebuilding its foundations one breaking release at a time

◆ Current state

inlabru wraps INLA for spatial, point-process and latent-Gaussian models in R. It is mid-modernisation: since 2.12.0 cut the sp stack, each release has renamed part of the public surface, standardised how external packages attach custom mappers, or replaced internal machinery. 2.15.0 is the latest step, pairing a new predictor evaluation and linearisation implementation with broom's tidy(), glance() and augment() methods and four non-zero-truncated observation families.

◆ Where it's heading

The arc is consolidation of the extension surface rather than expansion of the model catalogue. Every release adds mappers or families with one hand and removes a dependency, a re-export or a deprecated path with the other — plyr in 2.15.0, fmesher's Depends entry in 2.14.1, sp and ggmap in 2.12.0. The compatibility flag bru_compat_pre_2_14_enable and the temporary fm_int/fm_pixels re-exports show a maintainer sequencing breaks across releases instead of landing them together.

◆ Prediction

The 2.14 compatibility flag is still defaulting to TRUE and the fmesher re-exports are described in the entries as temporary, so the next obvious move is a release that flips bru_compat_pre_2_14_enable off and drops those re-exports.

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.

Alternatives to inlabru and rstudio.prefs

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 inlabru or rstudio.prefs.

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

Recent activity from inlabru and rstudio.prefs

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 agoinlabruPredictor linearisation rewritten; broom tidiers, truncated families
  3. 3mo agoinlabruBugfix release: factor contrasts, raster extraction, error classes
  4. 5mo agoinlabruNew mappers, standardised cgeneric support, bru_obs storage refactor
  5. 1y agoinlabruMapper classes shortened to bm_*, experimental predictor aggregation
  6. 1y agoinlabruDrops sp and ggmap for an sf-native spatial stack
  7. 4y agorstudio.prefsPreferences now read and written through rstudioapi
  8. 4y agorstudio.prefsConfig files left alone when nothing would change
  9. 4y agorstudio.prefsSecondary repositories can be deleted again
  10. 4y agorstudio.prefsRepository removal via NULL; config path helpers exported
  11. 5y agorstudio.prefsDocumentation, error messages, and array-type caution

Frequently asked questions

What is the difference between inlabru and rstudio.prefs?

They serve adjacent needs but don't currently overlap on shipped themes. inlabru and rstudio.prefs 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 inlabru better than rstudio.prefs?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. inlabru and rstudio.prefs 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 inlabru?

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

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.