neonUtilities
Two major versions shipped in a year, and this feed will not say what changed in either.
Comparison · Infra & APIs
inlabru vs prova
A side-by-side editorial comparison of inlabru and prova — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:api-consolidation
inlabru vs prova: 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 prova?
prova adds expected-utility calculation on top of its Bayesian inference core.
prova does Bayesian nonparametric inference in R — probabilities through Pr() and qPr(), mutual information, quantile plots. Five releases in about two weeks renamed its central argument, collapsed two plotting functions into one, and then in v2.3.0 introduced exputility() for expected utilities and their revisability, with plot() and print() methods attached from the start.
inlabru vs prova: 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.
prova
6.3INFRA · APIS
prova adds expected-utility calculation on top of its Bayesian inference core.
◆ Current state
prova does Bayesian nonparametric inference in R — probabilities through Pr() and qPr(), mutual information, quantile plots. Five releases in about two weeks renamed its central argument, collapsed two plotting functions into one, and then in v2.3.0 introduced exputility() for expected utilities and their revisability, with plot() and print() methods attached from the start.
◆ Where it's heading
Two arcs run in parallel. One compresses the API: learnt= became K=, flexiplot() and plotquantiles() merged into pplot(), and omitting arguments such as Y=, X= and K= got simpler. The other extends reach — mutualinfoF() for finite-domain variates, quantile accuracy reported alongside mutual information, and now a decision-theoretic layer sitting on the inference the package already did.
◆ Prediction
exputility() shipping with print() and plot() methods matches how the probability and mutual-information classes were treated, so utilities are likely to get the same class-based handling as they mature. The notes do not say whether decision analysis extends beyond expected utility.
Alternatives to inlabru and prova
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 prova.
Nematode
A nematode ecology toolbox whose last two releases corrected the arithmetic in its own indices.
modsem
modsem is grinding latent interaction models toward Mplus parity, one estimator at a time.
plssem
plssem took PLS-SEM into multilevel data, then spent two releases making the estimates trustworthy.
formr
formr's R client reached CRAN and moved its recommended path to the v1 REST API.
valr
valr's interval verbs now read genomic files in place instead of demanding a loaded tibble.
See all inlabru alternatives → · See all prova alternatives →
Recent activity from inlabru and prova
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 13d agoprovaexputility() brings decision analysis into prova ⚡
- 20d agoprovaCumulative 2.x notes, plus hist() and mutual-information changes
- 23d agoinlabruPredictor linearisation rewritten; broom tidiers, truncated families
- 23d agoprovalearnt= becomes K=; pplot() replaces two plot functions
- 27d agoprovaFix for pre-existing parallel clusters
- 28d agoprovaextraDistr dropped; mutual-information objects get a class
- 3mo agoinlabruBugfix release: factor contrasts, raster extraction, error classes
- 5mo agoinlabruNew mappers, standardised cgeneric support, bru_obs storage refactor
- 1y agoinlabruMapper classes shortened to bm_*, experimental predictor aggregation
- 1y agoinlabruDrops sp and ggmap for an sf-native spatial stack ⚡
Frequently asked questions
What is the difference between inlabru and prova?
Both compete on the same themes — api-consolidation — within Infra & APIs. prova is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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 prova?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. prova is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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 prova?
Top prova alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "prova alternatives" section above for the current picks, or visit /alternatives/prova for the full list with editorial commentary on each.