ggpointless
ggpointless keeps adding the ggplot2 layers nobody else bothered to write.
Comparison · Infra & APIs
inlabru vs watcher
A side-by-side editorial comparison of inlabru and watcher — release velocity, themes, recent moves, and the top alternatives to consider.
inlabru vs watcher: 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 watcher?
watcher is a thin filesystem-events binding whose releases are mostly build work.
The package wraps libfswatch in an R6 Watcher class for monitoring files and directories. Seven releases over sixteen months have added a vector path argument and two accessor methods, and spent the rest of their effort on build portability — non-standard system library locations, Windows bi-arch source builds on old rtools, and most recently removing the cmake requirement so the bundled source compiles with the R toolchain alone.
inlabru vs watcher: 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.
watcher
0.0INFRA · APIS
watcher is a thin filesystem-events binding whose releases are mostly build work.
◆ Current state
The package wraps libfswatch in an R6 Watcher class for monitoring files and directories. Seven releases over sixteen months have added a vector path argument and two accessor methods, and spent the rest of their effort on build portability — non-standard system library locations, Windows bi-arch source builds on old rtools, and most recently removing the cmake requirement so the bundled source compiles with the R toolchain alone.
◆ Where it's heading
The API is deliberately small and appears finished; the work that remains is making the C dependency install cleanly everywhere. Dropping cmake follows the same move nanonext made, which is not a coincidence — both come from the same author and both are aiming at environments where installing a build system is not an option.
◆ Prediction
With cmake gone and the bundled library current, further releases are most likely to track libfswatch upstream rather than extend the R interface.
Alternatives to inlabru and watcher
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 watcher.
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 inlabru alternatives → · See all watcher alternatives →
Recent activity from inlabru and watcher
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 23d agoinlabruPredictor linearisation rewritten; broom tidiers, truncated families
- 1mo agowatchercmake dropped from the bundled library build
- 3mo agowatcherBundled libfswatch updated to 1.20.1
- 3mo agoinlabruBugfix release: factor contrasts, raster extraction, error classes
- 5mo agoinlabruNew mappers, standardised cgeneric support, bru_obs storage refactor
- 8mo agowatcherWindows CPU usage fix for sub-second latency
- 1y agowatcherSystem libfswatch found in non-standard locations
- 1y agoinlabruMapper classes shortened to bm_*, experimental predictor aggregation
- 1y agowatcherMultiple paths per watcher, and older Windows builds fixed
- 1y agowatcherAccessor methods replace public Watcher fields
- 1y agoinlabruDrops sp and ggmap for an sf-native spatial stack ⚡
Frequently asked questions
What is the difference between inlabru and watcher?
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 watcher?
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 watcher?
Top watcher alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "watcher alternatives" section above for the current picks, or visit /alternatives/watcher for the full list with editorial commentary on each.