datefixR
The messy-date parser rewrote its core in Rust and came out 300x faster.
A side-by-side editorial comparison of parzer and sass — release velocity, themes, recent moves, and the top alternatives to consider.
A coordinate parser whose entire job is surviving how badly humans write latitude and longitude.
parzer converts messy coordinate strings — degrees, minutes, seconds, assorted symbols, arbitrary whitespace — into decimal degrees. Development is slow and sporadic, with three-year gaps between releases, and the work splits between C++ performance in the internal scrub() path and a long tail of parsing bugs. The most recent release, 0.4.4, fixed two genuinely dangerous ones: a leading space could silently drop a negative sign, and an E in a longitude string returned NA while a W parsed fine.
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.
parzer converts messy coordinate strings — degrees, minutes, seconds, assorted symbols, arbitrary whitespace — into decimal degrees. Development is slow and sporadic, with three-year gaps between releases, and the work splits between C++ performance in the internal scrub() path and a long tail of parsing bugs. The most recent release, 0.4.4, fixed two genuinely dangerous ones: a leading space could silently drop a negative sign, and an E in a longitude string returned NA while a W parsed fine.
The package has settled its scope — 0.4.1 explicitly rewrote the documentation to say it parses coordinates rather than validates them — and now moves only when someone finds a string it mishandles. Recent work has also been about shedding weight: Rcpp dependence reduced, the C++ requirement dropped from DESCRIPTION, suggested dependencies removed, and the vignette builder moved to Quarto. Maintainership passed to a new maintainer in 2022 and the package has stayed within rOpenSci.
The next release will most likely be another batch of parsing edge cases reported by users, since that is what every release since 0.2.0 has been. Nothing in these entries points to new functionality.
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.
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 parzer or sass.
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.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — maintenance — within Analytics. parzer and sass 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. parzer and sass 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 parzer alternatives in Analytics are ranked by recent ship velocity. Browse the "parzer alternatives" section above for the current picks, or visit /alternatives/parzer for the full list with editorial commentary on each.
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.