pr2database
The protist reference database keeps widening past the rRNA gene it was built on.
Comparison · Infra & APIs
inlabru vs tidyplots
A side-by-side editorial comparison of inlabru and tidyplots — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-packagebreaking-changes
inlabru vs tidyplots: at a glance
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.
What is tidyplots?
tidyplots keeps rebuilding its own foundations rather than layering around them.
tidyplots wraps ggplot2 in a pipe-driven API aimed at publication-ready scientific figures, trading grammar-of-graphics flexibility for a shorter path to a finished plot. It is at 0.4.0 after two years of frequent releases, and almost every one carries a breaking change — the most recent moved multi-panel layout off patchwork and onto ggplot2's own faceting. Statistical annotation, colour schemes and size control have each been reworked at least once.
inlabru vs tidyplots: editorial side-by-side
inlabru
2.5INFRA · APIS
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.
tidyplots
0.0INFRA · APIS
tidyplots keeps rebuilding its own foundations rather than layering around them.
◆ Current state
tidyplots wraps ggplot2 in a pipe-driven API aimed at publication-ready scientific figures, trading grammar-of-graphics flexibility for a shorter path to a finished plot. It is at 0.4.0 after two years of frequent releases, and almost every one carries a breaking change — the most recent moved multi-panel layout off patchwork and onto ggplot2's own faceting. Statistical annotation, colour schemes and size control have each been reworked at least once.
◆ Where it's heading
The package is converging on ggplot2 rather than abstracting away from it: split_plot() now uses facet_wrap and facet_grid, as_tidyplot() was hard-deprecated on the grounds that converting a ggplot was never a good idea, and releases are timed against upstream ggplot2 versions. The other constant is the statistics surface, which has grown from basic error bars to paired and selected comparisons. Breaking changes are announced plainly and frequently, consistent with a package using 0.x to fix its shape before committing.
◆ Prediction
The patchwork removal is described as something that will eventually break dependent code, so the near-term work is likely completing that migration and settling the split_plot() parameters introduced alongside it. A 1.0 would signal the breaking-change cadence is ending, and nothing here indicates that yet.
Alternatives to inlabru and tidyplots
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 tidyplots.
ggalign
Composable aligned layouts, rebuilt on S7 while ggplot2 4.0 lands underneath.
prioritizr
Conservation planning absorbs the literature's target-setting rules as code.
jSDM
Joint species distribution models in Gibbs-sampled C++, quiet since 2023.
rsofun
An ecosystem model starts tracking carbon isotopes and land-use change.
usmap
Ten years in, US mapping splits its data out and finally adds Puerto Rico.
See all inlabru alternatives → · See all tidyplots alternatives →
Recent activity from inlabru and tidyplots
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 23d agoinlabruPredictor linearisation rewritten; broom tidiers, truncated families
- 3mo agoinlabruBugfix release: factor contrasts, raster extraction, error classes
- 5mo agoinlabruNew mappers, standardised cgeneric support, bru_obs storage refactor
- 7mo agotidyplotstidyplots 0.4.0
- 1y agoinlabruMapper classes shortened to bm_*, experimental predictor aggregation
- 1y agotidyplotstidyplots 0.3.1
- 1y agotidyplotstidyplots 0.2.2
- 1y agotidyplotstidyplots 0.2.1
- 1y agotidyplotstidyplots 0.2.0
- 1y agoinlabruDrops sp and ggmap for an sf-native spatial stack ⚡
- 1y agotidyplotstidyplots 0.1.2
Frequently asked questions
What is the difference between inlabru and tidyplots?
Both compete on the same themes — r-package, breaking-changes — within Infra & APIs. inlabru is currently shipping more aggressively (velocity 2.5 vs 0.0), 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 inlabru better than tidyplots?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. inlabru is currently shipping more aggressively (velocity 2.5 vs 0.0), 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 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 tidyplots?
Top tidyplots alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "tidyplots alternatives" section above for the current picks, or visit /alternatives/tidyplots for the full list with editorial commentary on each.