rnaturalearth
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
Comparison · Analytics
Fulcrum vs mlr3tuning
A side-by-side editorial comparison of Fulcrum and mlr3tuning — release velocity, themes, recent moves, and the top alternatives to consider.
Fulcrum vs mlr3tuning: at a glance
| Feature | Fulcrum | mlr3tuning |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 2.5 |
| Sparks · 30d | 0 | 0 |
| Top themes | field-data-collection, esri-arcgis, offline-maps, on-device-inference | mlr3, hyperparameter-tuning, async-optimization, callbacks |
| Last editorial update | 20h ago | 1h ago |
| Website | — | Visit → |
What is Fulcrum?
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.
What is mlr3tuning?
mlr3tuning is rebuilding its async machinery under a stable public surface
mlr3tuning provides hyperparameter optimization for the mlr3 ecosystem, and its recent history is dominated by the asynchronous tuning path: archive freezing, callback stages around queue evaluation, and version-locked compatibility with the rush backend. Releases pair a small feature with several fixes and an explicit compatibility line naming the mlr3 or rush version they track. The most recent release drops all workarounds for older rush versions, which suggests that dependency has stabilized enough to require rather than accommodate.
Fulcrum vs mlr3tuning: editorial side-by-side
Fulcrum
6.3ANALYTICS
Fulcrum's mobile train is all Esri migration cleanup, with on-device inference quietly changing format.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
mlr3tuning
2.5ANALYTICS
mlr3tuning is rebuilding its async machinery under a stable public surface
◆ Current state
mlr3tuning provides hyperparameter optimization for the mlr3 ecosystem, and its recent history is dominated by the asynchronous tuning path: archive freezing, callback stages around queue evaluation, and version-locked compatibility with the rush backend. Releases pair a small feature with several fixes and an explicit compatibility line naming the mlr3 or rush version they track. The most recent release drops all workarounds for older rush versions, which suggests that dependency has stabilized enough to require rather than accommodate.
◆ Where it's heading
Two things are being tidied at once. The async archive is converging on a consistent data.table representation across batch and async variants, so results are shaped the same regardless of how tuning ran. Separately, the package is becoming a better ecosystem citizen — unioning tuner properties on load instead of overwriting them, removing its callbacks on unload, and raising informative errors from AutoTuner accessors on an untrained model. Both are the marks of a package used as a dependency more than as a destination.
◆ Prediction
With rush pinned to 1.2.0 and the compatibility shims gone, the next release is likely to expose more of the async path through callbacks rather than change the tuning interface.
Alternatives to Fulcrum and mlr3tuning
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 Fulcrum or mlr3tuning.
writexl
writexl spent nine years refusing to do formatting, then shipped all of it in 2.0.0.
rgbif
rgbif is steadily pushing users off paged searching and onto real downloads.
rstanarm
rstanarm is community-maintained now, tracking Stan and lme4 rather than adding models.
taxa
taxa started a ground-up rewrite in 2021 and has published almost nothing since.
rotl
rotl's whole release history is keeping name matching honest against a moving taxonomy.
See all Fulcrum alternatives → · See all mlr3tuning alternatives →
Recent activity from Fulcrum and mlr3tuning
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoFulcrumAndroid: update offline map layers in place, non-blocking Photo FastFill
- 2d agoFulcrumiOS fix: slow location resolution blocked record saves
- 6d agoFulcrumWeb: SSO email wording and ArcGIS/deck.gl version bumps
- 8d agoFulcrumAndroid fixes: ArcGIS stability, signature button, photo markup
- 8d agoFulcrumiOS fixes: basemap loading and black map screen
- 9d agoFulcrumiOS: ArcGIS SDK 300.0.0 and ONNX replaced by a new INFERENCE format
- 18d agomlr3tuningmlr3tuning 1.6.1 stops clobbering other packages' tuner properties
- 4mo agomlr3tuningmlr3tuning 1.6.0 aligns archive column order across tuning classes
- 8mo agomlr3tuningmlr3tuning 1.5.1 tracks xgboost 3.1.2.1
- 8mo agomlr3tuningmlr3tuning 1.5.0 adds queue evaluation stages to async callbacks
- 1y agomlr3tuningmlr3tuning 1.4.0 unifies logging under a base mlr3 logger
- 1y agomlr3tuningmlr3tuning 1.3.0 adds a frozen async archive and leaner worker storage
Frequently asked questions
What is the difference between Fulcrum and mlr3tuning?
They serve adjacent needs but don't currently overlap on shipped themes. Fulcrum is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 Fulcrum better than mlr3tuning?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Fulcrum is currently shipping more aggressively (velocity 6.3 vs 2.5), 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.
What are the best alternatives to Fulcrum?
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.
What are the best alternatives to mlr3tuning?
Top mlr3tuning alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3tuning alternatives" section above for the current picks, or visit /alternatives/mlr3tuning for the full list with editorial commentary on each.