writexl
writexl spent nine years refusing to do formatting, then shipped all of it in 2.0.0.
Comparison · Analytics
rnaturalearth vs rstanarm
A side-by-side editorial comparison of rnaturalearth and rstanarm — release velocity, themes, recent moves, and the top alternatives to consider.
rnaturalearth vs rstanarm: at a glance
What is rnaturalearth?
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
1.0.0 ended sp support outright, making sf the default and offering terra's SpatVector via `returnclass`, after 0.3.3 had signposted that with lifecycle badges. The two releases since move to delivery mechanics: 1.1.0 reads data directly out of the zip through the GDAL Virtual File System, starts moving unloaded downloads to GeoPackage instead of shapefile, and switches the base URL to naciscdn.org; 1.2.0 adds caching to `ne_download()` when `destdir` is persistent, swaps devtools for pak when installing the companion data packages, and handles Natural Earth's inconsistent raster zip layouts.
What is rstanarm?
rstanarm is community-maintained now, tracking Stan and lme4 rather than adding models.
2.32.2 is entirely infrastructure and dependency work: formula machinery migrated from lme4 to reformulas, `r_eff` no longer computed for loo by default, the Stan R packages repo replaced by R-Universe, rstantools adopted to fix build and export errors, and CRAN NOTE cleanups — contributed largely by four first-time contributors. 2.32.1 and 2.26.1 follow the same pattern, tracking rstan syntax and adding `posterior::as_draws()` support. The last release with substantive modelling content is 2.21.1, which changed how default priors are determined and flipped `autoscale` to FALSE outside default priors.
rnaturalearth vs rstanarm: editorial side-by-side
rnaturalearth
0.0ANALYTICS
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
◆ Current state
1.0.0 ended sp support outright, making sf the default and offering terra's SpatVector via `returnclass`, after 0.3.3 had signposted that with lifecycle badges. The two releases since move to delivery mechanics: 1.1.0 reads data directly out of the zip through the GDAL Virtual File System, starts moving unloaded downloads to GeoPackage instead of shapefile, and switches the base URL to naciscdn.org; 1.2.0 adds caching to `ne_download()` when `destdir` is persistent, swaps devtools for pak when installing the companion data packages, and handles Natural Earth's inconsistent raster zip layouts.
◆ Where it's heading
With the class question settled, the work has shifted to not re-downloading and not unpacking — VFS reads, caching, and a container format that does not need a sidecar of four files. That points at the package being used in repeated or automated contexts rather than interactive one-offs. The shapefile-to-GeoPackage transition is explicitly incomplete.
◆ Prediction
Completing the GeoPackage transition for `load = FALSE` downloads is the obvious next step, since 1.1.0 described it as in progress.
rstanarm
0.0ANALYTICS
rstanarm is community-maintained now, tracking Stan and lme4 rather than adding models.
◆ Current state
2.32.2 is entirely infrastructure and dependency work: formula machinery migrated from lme4 to reformulas, `r_eff` no longer computed for loo by default, the Stan R packages repo replaced by R-Universe, rstantools adopted to fix build and export errors, and CRAN NOTE cleanups — contributed largely by four first-time contributors. 2.32.1 and 2.26.1 follow the same pattern, tracking rstan syntax and adding `posterior::as_draws()` support. The last release with substantive modelling content is 2.21.1, which changed how default priors are determined and flipped `autoscale` to FALSE outside default priors.
◆ Where it's heading
The package has moved from feature development into ecosystem maintenance, and the contributor list shows why it survives: outside developers keep it compiling against a moving Stan, lme4 and CRAN. The `as_draws()` support and the reformulas migration both point the same way — rstanarm increasingly consumes shared infrastructure (posterior, reformulas, rstantools) instead of carrying its own.
◆ Prediction
Expect the next release to track another upstream change — rstan, reformulas or CRAN policy — rather than add model families. The pre-fit model surface looks settled.
Alternatives to rnaturalearth and rstanarm
Other Analytics 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 rnaturalearth or rstanarm.
rgbif
rgbif is steadily pushing users off paged searching and onto real downloads.
taxa
taxa started a ground-up rewrite in 2021 and has published almost nothing since.
rotl
rotl's whole release history is keeping name matching honest against a moving taxonomy.
taxize
taxize spends its releases absorbing other people's API changes, one dead source at a time.
osmdata
osmdata keeps tightening its Overpass query surface, breaking small things to get types right.
See all rnaturalearth alternatives → · See all rstanarm alternatives →
Recent activity from rnaturalearth and rstanarm
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 6mo agornaturalearthrnaturalearth 1.2.0
- 10mo agorstanarmrstanarm 2.32.2 migrates formula machinery to reformulas
- 1y agornaturalearthrnaturalearth 1.1.0
- 2y agorstanarmrstanarm 2.32.1 fixes unit_vector error, enables LTO
- 2y agornaturalearthrnaturalearth 1.0.0 drops sp for sf and terra
- 2y agorstanarmrstanarm 2.26.1 adopts new rstan syntax and as_draws()
- 3y agornaturalearthrnaturalearth 0.3.3 deprecates sp, imports terra
- 4y agorstanarmrstanarm 2.21.3 fixes loo() and adds stan_jm offsets
- 6y agorstanarmrstanarm 2.21.1 changes default prior behaviour
Frequently asked questions
What is the difference between rnaturalearth and rstanarm?
They serve adjacent needs but don't currently overlap on shipped themes. rnaturalearth and rstanarm are shipping at a similar cadence (velocity 0.0 vs 0.0, 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 rnaturalearth better than rstanarm?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rnaturalearth and rstanarm are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to rnaturalearth?
Top rnaturalearth alternatives in Analytics are ranked by recent ship velocity. Browse the "rnaturalearth alternatives" section above for the current picks, or visit /alternatives/rnaturalearth for the full list with editorial commentary on each.
What are the best alternatives to rstanarm?
Top rstanarm alternatives in Analytics are ranked by recent ship velocity. Browse the "rstanarm alternatives" section above for the current picks, or visit /alternatives/rstanarm for the full list with editorial commentary on each.