ggpointless
ggpointless keeps adding the ggplot2 layers nobody else bothered to write.
Comparison · Infra & APIs
rstudio.prefs vs Tailscale
A side-by-side editorial comparison of rstudio.prefs and Tailscale — release velocity, themes, recent moves, and the top alternatives to consider.
rstudio.prefs vs Tailscale: at a glance
| Feature | rstudio.prefs | Tailscale |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 2.5 | 6.3 |
| Sparks · 30d | 0 | 0 |
| Top themes | r-packages, rstudio, developer-tools, configuration-as-code | networking, scale, api, kubernetes |
| Last editorial update | 1h ago | 4h ago |
| Website | 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.
What is Tailscale?
Tailscale is paying down scale in two dimensions: nodes per tailnet, tailnets per org.
Three threads run through this window. The tailnet management API is the newest: creation landed in alpha in late July, and the list endpoint now paginates at 100 results with limit and cursor parameters. The client releases are patch-grade but weighted toward scale — v1.102.1 made node additions and removals constant-time, and v1.102.3 fixes Tailnet Lock startup failures on large tailnets while cutting memory use on iOS and tvOS. The Kubernetes operator runs on its own track, adding in-cluster PeerRelays, workload identity federation and IPv6 egress.
rstudio.prefs vs Tailscale: editorial side-by-side
rstudio.prefs
2.5INFRA · APIS
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.
Tailscale
6.3INFRA · APIS
Tailscale is paying down scale in two dimensions: nodes per tailnet, tailnets per org.
◆ Current state
Three threads run through this window. The tailnet management API is the newest: creation landed in alpha in late July, and the list endpoint now paginates at 100 results with limit and cursor parameters. The client releases are patch-grade but weighted toward scale — v1.102.1 made node additions and removals constant-time, and v1.102.3 fixes Tailnet Lock startup failures on large tailnets while cutting memory use on iOS and tvOS. The Kubernetes operator runs on its own track, adding in-cluster PeerRelays, workload identity federation and IPv6 egress.
◆ Where it's heading
The qualifier that keeps recurring is “large”: tailnets big enough to break Tailnet Lock at startup, node churn that pinned CPU, mobile clients running short of memory, and organizations holding more than a hundred tailnets. Tailscale is absorbing the cost of customers who outgrew the shape the product originally assumed, in two directions at once — nodes inside a tailnet, and tailnets inside an organization. The second is the more consequential, because allocating a tailnet per customer or per environment is a different product than a company network. Security work stays continuous alongside it, with TS-2026-011 closed here and a run of SSH and Serve advisories backported the month before.
◆ Prediction
The tailnet creation API should leave alpha carrying the same limit-and-cursor contract just applied to the list endpoint, with further startup and memory work aimed at large tailnets on the client side.
Alternatives to rstudio.prefs and Tailscale
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 Tailscale.
mpactr
mpactr spent two spring releases normalizing case in metadata after users kept tripping on it.
surveytidy
surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.
surveycore
surveycore declared its API stable with every survey design type covered.
PEIMAN2
PEIMAN2 cut its annotation database loose from its release cycle without breaking CRAN.
prospectr
prospectr spent its biggest release in years fixing spectra it had been quietly mangling.
See all rstudio.prefs alternatives → · See all Tailscale alternatives →
Recent activity from rstudio.prefs and Tailscale
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 7h agorstudio.prefsShortcut removal, an addins.json fix, and a new maintainer
- 1d agoTailscalev1.102.3 patches a 4via6 routing flaw and large-tailnet startups
- 2d agoTailscaleTailnet list API pagination
- 9d agoTailscaleOperator adds in-cluster PeerRelays and workload identity federation
- 13d agoTailscaleContainer image v1.102.2: library updates only
- 16d agoTailscalev1.102.2 fixes a Funnel incoming-connection regression
- 17d agoTailscalev1.102.1 adds Services CLI and constant-time node churn
- 4y agorstudio.prefsPreferences now read and written through rstudioapi
- 4y agorstudio.prefsConfig files left alone when nothing would change
- 4y agorstudio.prefsSecondary repositories can be deleted again
- 4y agorstudio.prefsRepository removal via NULL; config path helpers exported
- 5y agorstudio.prefsDocumentation, error messages, and array-type caution
Frequently asked questions
What is the difference between rstudio.prefs and Tailscale?
They serve adjacent needs but don't currently overlap on shipped themes. Tailscale is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 rstudio.prefs better than Tailscale?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Tailscale is currently shipping more aggressively (velocity 6.3 vs 2.5), with 0 editorial sparks in the last 30 days against 0. 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 Tailscale?
Top Tailscale alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Tailscale alternatives" section above for the current picks, or visit /alternatives/tailscale for the full list with editorial commentary on each.