leaflet
leaflet relicensed to MIT and finished migrating off R's retired spatial stack
A side-by-side editorial comparison of Fulcrum and themis — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Fulcrum | themis |
|---|---|---|
| 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 | r, tidymodels, class-imbalance, resampling |
| Last editorial update | 15h ago | 1h ago |
| Website | — | Visit → |
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.
themis is back to adding real resampling algorithms after a documentation-heavy stretch.
themis supplies recipes steps for handling class imbalance in tidymodels. The 1.0.x line was consumed by documentation accuracy, message translation and internal consistency work. Version 1.1.0 returns to substance with two new under-sampling methods.
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.
themis supplies recipes steps for handling class imbalance in tidymodels. The 1.0.x line was consumed by documentation accuracy, message translation and internal consistency work. Version 1.1.0 returns to substance with two new under-sampling methods.
The package grows by adding algorithms rather than restructuring itself. tomek() was rewritten to handle multiple classes and drop the unbalanced dependency, case weights arrived at 1.0.0, and cluster-centroid and condensed-nearest-neighbour under-sampling arrive now — each shipped as both a recipes step and a direct-implementation function.
Expect further under- and over-sampling methods in the same paired form, as the package fills out coverage of the standard class-imbalance literature.
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 themis.
leaflet relicensed to MIT and finished migrating off R's retired spatial stack
ggpubr reached 1.0.0 with p-value formatting presets for specific journals
bigrquery went MIT, then handed its slowest path to the BigQuery Storage API
sparklyr now spends its releases absorbing dbplyr changes and feeding pysparklyr
Seurat's centre of gravity has moved from single cells to spatial data and on-disk matrices
insight quietly widens the set of model objects the easystats ecosystem can read
See all Fulcrum alternatives → · See all themis 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 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.
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.
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.
Top themis alternatives in Analytics are ranked by recent ship velocity. Browse the "themis alternatives" section above for the current picks, or visit /alternatives/themis for the full list with editorial commentary on each.