datefixR
The messy-date parser rewrote its core in Rust and came out 300x faster.
A side-by-side editorial comparison of sass and waywiser — release velocity, themes, recent moves, and the top alternatives to consider.
Nine releases of compiler warnings and CRAN checks — the Sass binding is in pure upkeep.
sass compiles Sass to CSS for R, and its recent history is almost entirely about staying installable. The last ten releases are dominated by compilation warnings on new toolchains — Apple Clang 15, gcc-12, Windows — plus R CMD check fixes for r-devel and one LibSass version bump. The only user-visible changes in the set are the switch to woff2 font files in font_google(local = TRUE) and clearer output when Google fonts are downloaded.
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.
sass compiles Sass to CSS for R, and its recent history is almost entirely about staying installable. The last ten releases are dominated by compilation warnings on new toolchains — Apple Clang 15, gcc-12, Windows — plus R CMD check fixes for r-devel and one LibSass version bump. The only user-visible changes in the set are the switch to woff2 font files in font_google(local = TRUE) and clearer output when Google fonts are downloaded.
This is a stable binding to a C++ library that is itself no longer moving, so the package's work is defined by the compilers and CRAN policies around it rather than by Sass features. Nothing in these entries suggests active development; the maintenance is competent and prompt, but it is maintenance.
The next release will most likely be triggered by a new compiler warning class or an R CMD check requirement rather than by anything in the Sass language. The entries give no signal of planned feature work.
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.
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.
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.
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 sass or waywiser.
The messy-date parser rewrote its core in Rust and came out 300x faster.
The legend engine mapsf spun out, now covering legend types the parent map package can draw.
R help pages translated on demand by whichever LLM you point it at.
Thematic mapping in base R that finally got a theming system, then spent two years polishing legends.
qualtRics moved its contact functions onto XM Directory days before the old endpoints died.
The tidyverts forecasting core rebuilt model combination on full residual covariance.
See all sass alternatives → · See all waywiser alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. sass and waywiser are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. sass and waywiser are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top sass alternatives in Analytics are ranked by recent ship velocity. Browse the "sass alternatives" section above for the current picks, or visit /alternatives/sass for the full list with editorial commentary on each.
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.