ggpointless
ggpointless keeps adding the ggplot2 layers nobody else bothered to write.
Comparison · Infra & APIs
fastpos vs inlabru
A side-by-side editorial comparison of fastpos and inlabru — release velocity, themes, recent moves, and the top alternatives to consider.
fastpos vs inlabru: at a glance
What is fastpos?
Dormant three years, then a two-line release nobody using it would notice
fastpos finds the critical point of stability for a Pearson correlation, a simulation problem whose C++ implementation is the entire reason the package exists. Its substantive work concluded in 2022 with 0.5.0, the release prepared during R Journal review, which renamed the precision parameters, moved multicore work to pbapply and let users set corridor limits directly. After three years of silence, 0.6.0 removes an internal restriction to cpp11 and changes index_pop to an integer.
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.
fastpos vs inlabru: editorial side-by-side
fastpos
0.0INFRA · APIS
Dormant three years, then a two-line release nobody using it would notice
◆ Current state
fastpos finds the critical point of stability for a Pearson correlation, a simulation problem whose C++ implementation is the entire reason the package exists. Its substantive work concluded in 2022 with 0.5.0, the release prepared during R Journal review, which renamed the precision parameters, moved multicore work to pbapply and let users set corridor limits directly. After three years of silence, 0.6.0 removes an internal restriction to cpp11 and changes index_pop to an integer.
◆ Where it's heading
This is a finished piece of research software in low-effort upkeep. The changelog's centre of gravity is the R Journal review process, and once that concluded the package stopped changing. The single release since is toolchain work of the kind that keeps a package compiling rather than anything a user would see.
◆ Prediction
Expect nothing beyond occasional compilation or CRAN-check fixes unless the accompanying paper draws requests for other correlation types or resampling schemes.
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.
Alternatives to fastpos and inlabru
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 fastpos or inlabru.
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 fastpos alternatives → · See all inlabru alternatives →
Recent activity from fastpos and inlabru
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
- 10mo agofastposcpp11 restriction removed; index_pop now an integer
- 1y agoinlabruMapper classes shortened to bm_*, experimental predictor aggregation
- 1y agoinlabruDrops sp and ggmap for an sf-native spatial stack ⚡
- 4y agofastposMulticore fix for pbmcapply; Windows limited to one core
- 4y agofastposR Journal review release: renamed precision parameters, manual corridor limits
- 5y agofastposMore informative test failures; interactive-only progress bars
- 6y agofastposMulticore support via the future package
- 6y agofastposExact-rho population generation and C++ progress bar fixes
Frequently asked questions
What is the difference between fastpos and inlabru?
They serve adjacent needs but don't currently overlap on shipped themes. 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 fastpos better than inlabru?
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 fastpos?
Top fastpos alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "fastpos alternatives" section above for the current picks, or visit /alternatives/fastpos for the full list with editorial commentary on each.
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.