mlr3mbo
mlr3mbo picked its defaults from a benchmark study, not from taste
A side-by-side editorial comparison of easystats and Fulcrum — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | easystats | Fulcrum |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 0.0 | 6.3 |
| Sparks · 30d | 0 | 0 |
| Top themes | r ecosystem, meta-package, statistical reporting, licensing | field-data-collection, esri-arcgis, offline-maps, on-device-inference |
| Last editorial update | 1h ago | 17h ago |
| Website | Visit → | — |
The easystats meta-package is install tooling wrapped around a relicensed ecosystem.
easystats is the meta-package for the easystats ecosystem, which spans insight, parameters, performance and their siblings. It ships almost no statistics of its own; its releases add installation helpers, ecosystem introspection functions and vignettes. The consequential release in this window is 0.7.0, which moved the whole ecosystem to an MIT license.
Fulcrum's mobile train is all Esri migration cleanup, with on-device inference quietly changing format.
Fulcrum ships iOS, Android, and web releases on a near-weekly cadence, and this stretch is dominated by mapping work following the Google Maps retirement announced for September. Recent builds upgraded to ArcGIS SDK 300.0.0, moved the web map engine to current ArcGIS and deck.gl versions, and worked through the resulting stability issues — basemap loading, location resolution, black map screens, panning and zooming performance. The most consequential change is easy to miss: ONNX support for on-device machine learning inference was removed in favor of a new INFERENCE format that reads labels from an uploaded labels.txt.
easystats is the meta-package for the easystats ecosystem, which spans insight, parameters, performance and their siblings. It ships almost no statistics of its own; its releases add installation helpers, ecosystem introspection functions and vignettes. The consequential release in this window is 0.7.0, which moved the whole ecosystem to an MIT license.
Work concentrates on making the ecosystem legible and installable as a unit: easystats_packages() to enumerate it, easystats_citations() to count its citations, pak and r-universe support to install it, and a complete-workflow vignette to show it in use. Underneath that, 0.7.0 settled the licensing and formalized the author list. The pattern is a project tending its own boundaries rather than adding capability.
The recent additions are all introspection and installation helpers, so the next release most likely adds another of those or refreshes component versions rather than changing what the ecosystem does.
Fulcrum ships iOS, Android, and web releases on a near-weekly cadence, and this stretch is dominated by mapping work following the Google Maps retirement announced for September. Recent builds upgraded to ArcGIS SDK 300.0.0, moved the web map engine to current ArcGIS and deck.gl versions, and worked through the resulting stability issues — basemap loading, location resolution, black map screens, panning and zooming performance. The most consequential change is easy to miss: ONNX support for on-device machine learning inference was removed in favor of a new INFERENCE format that reads labels from an uploaded labels.txt.
This is a platform consolidation being paid down one point release at a time. Having committed to Esri, Fulcrum is absorbing the instability that came with it, and each release reads as fixes to symptoms of the same migration. Underneath, the offline and field-capture story continues to get real attention — downloaded offline map layers can now be updated in place, and Photo FastFill moved to background processing so it no longer blocks editing.
Expect the release notes to stay fix-dominated through the September Google Maps cutoff, with the migration-related map defects tapering after it passes. Photo FastFill leaving early access is the most likely next substantive item.
Other Analytics 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 easystats or Fulcrum.
mlr3mbo picked its defaults from a benchmark study, not from taste
loo keeps rewriting the diagnostics Bayesian modellers read off model comparison
mlr3fselect turned feature selection into an asynchronous, distributable job
lime survives on compatibility patches years after its research moment
mlr3measures is systematically retrofitting sample weights across every metric
mlr3cluster went from a handful of clusterers to covering the field
See all easystats alternatives → · See all Fulcrum alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Fulcrum is currently shipping more aggressively (velocity 6.3 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Fulcrum is currently shipping more aggressively (velocity 6.3 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 Analytics products to evaluate alongside.
Top easystats alternatives in Analytics are ranked by recent ship velocity. Browse the "easystats alternatives" section above for the current picks, or visit /alternatives/easystats for the full list with editorial commentary on each.
Top Fulcrum alternatives in Analytics are ranked by recent ship velocity. Browse the "Fulcrum alternatives" section above for the current picks, or visit /alternatives/fulcrum for the full list with editorial commentary on each.