← Back to home
Comparison · Infra & APIs

inlabru vs ShortForm

A side-by-side editorial comparison of inlabru and ShortForm — release velocity, themes, recent moves, and the top alternatives to consider.

inlabru vs ShortForm: at a glance

FeatureinlabruShortForm
SectorInfra & APIsInfra & APIs
Velocity score2.50.0
Sparks · 30d00
Top themesbayesian-modelling, spatial-statistics, r-package, api-consolidationpsychometrics, scale-construction, optimization-algorithms, lavaan
Last editorial update47m ago1h ago
WebsiteVisit →Visit →

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.

Read the full inlabru trajectory →

What is ShortForm?

Automated scale shortening with lavaan, spending its releases repairing its own search algorithms.

ShortForm automates the creation of short-form psychometric scales by searching for well-fitting subsets of items, using ant colony optimization, simulated annealing and Tabu search over lavaan models. The recent releases are corrective: 0.5.7 fixed the ant colony algorithm failing to update its best model and the simulated annealing routine mis-specifying models containing factor relationships or outcome variables, and 0.5.8 fixed Tabu search under parallel workflows and with multidimensional models. Each release note carries an explicit roadmap listing refactoring for 0.6.0 and input standardisation for 0.7.0, neither of which has shipped.

Read the full ShortForm trajectory →

inlabru vs ShortForm: editorial side-by-side

I
inlabru
INFRA · APIS
2.5

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.

S
ShortForm
INFRA · APIS
0.0

Automated scale shortening with lavaan, spending its releases repairing its own search algorithms.

◆ Current state

ShortForm automates the creation of short-form psychometric scales by searching for well-fitting subsets of items, using ant colony optimization, simulated annealing and Tabu search over lavaan models. The recent releases are corrective: 0.5.7 fixed the ant colony algorithm failing to update its best model and the simulated annealing routine mis-specifying models containing factor relationships or outcome variables, and 0.5.8 fixed Tabu search under parallel workflows and with multidimensional models. Each release note carries an explicit roadmap listing refactoring for 0.6.0 and input standardisation for 0.7.0, neither of which has shipped.

◆ Where it's heading

The defects being fixed are in the search itself rather than around it. An optimizer that does not correctly retain its best candidate, and a search that mis-specifies models after the first iteration, both produce plausible-looking short forms that are not the ones the method should have found, which is a harder class of problem to notice than a crash. Alongside that the package is shedding dependencies, with ggplot2, ggrepel and tidyr dropped from the plotting methods in 0.5.8. The stated intent to refactor the major functions and standardise their arguments suggests the maintainer regards the current interface as the obstacle to further work.

◆ Prediction

The roadmap repeated across these notes points to a 0.6.0 focused on refactoring the major functions, with argument and output standardisation deferred to 0.7.0. On the evidence of this window, more unit tests and further algorithm-level fixes are likelier to arrive first than either milestone.

Alternatives to inlabru and ShortForm

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 ShortForm.

See all inlabru alternatives → · See all ShortForm alternatives →

Recent activity from inlabru and ShortForm

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 23d agoinlabruPredictor linearisation rewritten; broom tidiers, truncated families
  2. 3mo agoinlabruBugfix release: factor contrasts, raster extraction, error classes
  3. 3mo agoShortFormTabu search fixed for parallel and multidimensional models
  4. 3mo agoShortFormAnt colony search failed to retain its best model
  5. 5mo agoinlabruNew mappers, standardised cgeneric support, bru_obs storage refactor
  6. 1y agoinlabruMapper classes shortened to bm_*, experimental predictor aggregation
  7. 1y agoShortFormlavaan model specification defaults made forgiving
  8. 1y agoinlabruDrops sp and ggmap for an sf-native spatial stack
  9. 2y agoShortFormCompatibility fixes for a new lavaan release
  10. 2y agoShortFormAdapted to changed lavaan error and warning messages
  11. 2y agoShortFormDefault specification tweaks and documentation fixes

Frequently asked questions

What is the difference between inlabru and ShortForm?

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 inlabru better than ShortForm?

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 ShortForm?

Top ShortForm alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ShortForm alternatives" section above for the current picks, or visit /alternatives/shortform for the full list with editorial commentary on each.