rnaturalearth
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
Comparison · Analytics
patchwork vs rstanarm
A side-by-side editorial comparison of patchwork and rstanarm — release velocity, themes, recent moves, and the top alternatives to consider.
patchwork vs rstanarm: at a glance
What is patchwork?
patchwork stopped being a ggplot composer and became a page composer.
patchwork assembles plots into compositions with arithmetic operators, and the 1.x line has steadily hardened that grammar: guide and axis collection, free() to exempt a plot from alignment, inset_element() for overlays, and list-like behaviour so lapply() and length() work on a patchwork. Version 1.3.0 added native gt table support. The two releases since are a load-time warning fix and a compatibility pass for the next ggplot2 release.
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.
patchwork vs rstanarm: editorial side-by-side
patchwork
0.0ANALYTICS
patchwork stopped being a ggplot composer and became a page composer.
◆ Current state
patchwork assembles plots into compositions with arithmetic operators, and the 1.x line has steadily hardened that grammar: guide and axis collection, free() to exempt a plot from alignment, inset_element() for overlays, and list-like behaviour so lapply() and length() work on a patchwork. Version 1.3.0 added native gt table support. The two releases since are a load-time warning fix and a compatibility pass for the next ggplot2 release.
◆ Where it's heading
The centre of gravity is shifting from alignment mechanics to composition scope. Early releases were almost entirely bug fixes against grid and ggplot2 internals — strip placement, fixed aspect ratios, guide merging. Recent ones add object types and escape hatches instead. Between feature cycles the package is in maintenance defined by ggplot2's release calendar, which is what 1.3.1 is in its entirety.
◆ Prediction
Expect wrap_table() to grow beyond gt to other table objects, and expect the next substantive release to be triggered by a ggplot2 internals change rather than by a patchwork roadmap.
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 patchwork 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 patchwork or rstanarm.
writexl
writexl spent nine years refusing to do formatting, then shipped all of it in 2.0.0.
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.
See all patchwork alternatives → · See all rstanarm alternatives →
Recent activity from patchwork and rstanarm
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 10mo agorstanarmrstanarm 2.32.2 migrates formula machinery to reformulas
- 11mo agopatchworkFix spurious load-time warnings
- 1y agopatchworkCompatibility pass for the next ggplot2 release
- 1y agopatchworkgt tables become first-class patchwork objects ⚡
- 2y agorstanarmrstanarm 2.32.1 fixes unit_vector error, enables LTO
- 2y agopatchworkAxis collection and free() arrive
- 2y agorstanarmrstanarm 2.26.1 adopts new rstan syntax and as_draws()
- 3y agopatchworkPatchworks behave like lists; NULL becomes a no-op
- 3y agopatchworkClearer error when plotting space is too small
- 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 patchwork and rstanarm?
They serve adjacent needs but don't currently overlap on shipped themes. patchwork 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 patchwork better than rstanarm?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. patchwork 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 patchwork?
Top patchwork alternatives in Analytics are ranked by recent ship velocity. Browse the "patchwork alternatives" section above for the current picks, or visit /alternatives/patchwork 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.