datefixR
The messy-date parser rewrote its core in Rust and came out 300x faster.
Comparison · Analytics
waywiser vs xplainfi
A side-by-side editorial comparison of waywiser and xplainfi — release velocity, themes, recent moves, and the top alternatives to consider.
waywiser vs xplainfi: at a glance
What is waywiser?
Spatial model assessment that spent the last year on cross-platform arithmetic and CRAN rules.
waywiser provides spatial model assessment metrics in a tidymodels idiom — spatial autocorrelation measures, area of applicability, and multi-scale assessment of predictions. The substantive work landed in 0.3.0 through 0.5.0, and the recent releases are consolidation: 0.6.0 made metric functions return NA everywhere they previously returned NaN, because macOS disagreed with every other platform, and taught ww_multi_scale() to handle classification and class probability metrics correctly when given rasters. The three releases since are entirely CRAN policy compliance — no internet downloads during checks, no writing to directories, no syntax that would raise the R version floor.
What is xplainfi?
xplainfi treats feature importance as an estimate with error bars, not a number.
xplainfi implements feature importance methods for mlr3 — perturbation-based PFI, CFI and RFI, refit-based LOCO and WVIM, and SAGE. Its defining choice is that importance scores come with inference attached: several confidence-interval methods, including the Nadeau-Bengio correction and a distribution-free option added in 1.1.0. It declared itself released at 1.0.0 in January 2026.
waywiser vs xplainfi: editorial side-by-side
waywiser
0.0ANALYTICS
Spatial model assessment that spent the last year on cross-platform arithmetic and CRAN rules.
◆ Current state
waywiser provides spatial model assessment metrics in a tidymodels idiom — spatial autocorrelation measures, area of applicability, and multi-scale assessment of predictions. The substantive work landed in 0.3.0 through 0.5.0, and the recent releases are consolidation: 0.6.0 made metric functions return NA everywhere they previously returned NaN, because macOS disagreed with every other platform, and taught ww_multi_scale() to handle classification and class probability metrics correctly when given rasters. The three releases since are entirely CRAN policy compliance — no internet downloads during checks, no writing to directories, no syntax that would raise the R version floor.
◆ Where it's heading
The package has reached the point where the interesting bugs are cross-platform and cross-package rather than statistical. Its main function, ww_multi_scale(), has been the focus of nearly every release since 0.4.0, working through units handling, aggregation ordering, raster inputs and metric-type dispatch. The dependency on vip and the tidymodels metric machinery means a share of releases exist only to track breaking changes elsewhere.
◆ Prediction
Expect the next substantive release to continue on ww_multi_scale() edge cases, given that it has absorbed most of the fixes in this window. The recent run of CRAN-compliance patches suggests no feature work is currently in flight.
xplainfi
2.5ANALYTICS
xplainfi treats feature importance as an estimate with error bars, not a number.
◆ Current state
xplainfi implements feature importance methods for mlr3 — perturbation-based PFI, CFI and RFI, refit-based LOCO and WVIM, and SAGE. Its defining choice is that importance scores come with inference attached: several confidence-interval methods, including the Nadeau-Bengio correction and a distribution-free option added in 1.1.0. It declared itself released at 1.0.0 in January 2026.
◆ Where it's heading
Two lines of work run in parallel. The statistical side keeps adding inference options — variance corrections, conditional predictive impact, and the Lei et al. observation-wise loss-difference test — while the computational side attacks the cost of refit-based methods, most recently with a batch_size argument that parallelises refits and a default of one refit per resampling iteration. Support for pre-trained learners in 1.1.0 removes the refit requirement entirely in some workflows.
◆ Prediction
The stated reasoning that budget is better spent on resampling iterations than repeated refits suggests n_repeats may be removed from WVIM and LOCO outright, as the release notes hint.
Alternatives to waywiser and xplainfi
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 waywiser or xplainfi.
maplegend
The legend engine mapsf spun out, now covering legend types the parent map package can draw.
lang
R help pages translated on demand by whichever LLM you point it at.
mapsf
Thematic mapping in base R that finally got a theming system, then spent two years polishing legends.
qualtRics
qualtRics moved its contact functions onto XM Directory days before the old endpoints died.
fabletools
The tidyverts forecasting core rebuilt model combination on full residual covariance.
See all waywiser alternatives → · See all xplainfi alternatives →
Recent activity from waywiser and xplainfi
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 20d agoxplainfiRefits parallelise; repeated refits deprioritised in favour of resampling
- 5mo agoxplainfiPre-trained learners supported; distribution-free inference added
- 6mo agoxplainfiVersion bumped to mark the package as released
- 9mo agoxplainfiConfidence intervals arrive for feature importance scores
- 1y agowaywiserStops downloading data during CRAN checks
- 1y agowaywiserVignettes no longer write to CRAN directories
- 1y agowaywiserKeeps the R version floor below 4.1
- 2y agowaywiserNaN results become NA; raster metrics dispatch correctly
- 2y agowaywiserGuards against ignored grid arguments; faster on sf data
- 2y agowaywiserFixes wrong observation counts and ignored grid units
Frequently asked questions
What is the difference between waywiser and xplainfi?
They serve adjacent needs but don't currently overlap on shipped themes. xplainfi 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 waywiser better than xplainfi?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. xplainfi 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 Analytics products to evaluate alongside.
What are the best alternatives to waywiser?
Top waywiser alternatives in Analytics are ranked by recent ship velocity. Browse the "waywiser alternatives" section above for the current picks, or visit /alternatives/waywiser for the full list with editorial commentary on each.
What are the best alternatives to xplainfi?
Top xplainfi alternatives in Analytics are ranked by recent ship velocity. Browse the "xplainfi alternatives" section above for the current picks, or visit /alternatives/xplainfi for the full list with editorial commentary on each.