datefixR
The messy-date parser rewrote its core in Rust and came out 300x faster.
A side-by-side editorial comparison of beautier and sftime — release velocity, themes, recent moves, and the top alternatives to consider.
A BEAST2 XML generator shipping releases CRAN can't accept because the CRAN team is on holiday.
beautier turns R code into BEAST2 phylogenetics XML input files. The three most recent releases landed over four days in August 2025 and are all explicitly marked pre-CRAN, held back because the CRAN team was on summer holiday. The substance sits in 2.6.13, which added tip-date file handling; the two after it are lint and bug fixes.
The spatiotemporal companion to sf, moving at the pace of the packages around it.
sftime extends sf with an active time column, giving R a data frame class for data that is both spatial and temporal. Its recent history is almost entirely integration work: 0.3.0 added conversion methods from spatstat point patterns, sftrack and sftraj movement objects and cubble data frames, plus dedicated tidyr::drop_na() and dplyr::dplyr_reconstruct() methods. The two releases since are a namespace version-check correction and a switch from the magrittr pipe to the native pipe in examples.
beautier turns R code into BEAST2 phylogenetics XML input files. The three most recent releases landed over four days in August 2025 and are all explicitly marked pre-CRAN, held back because the CRAN team was on summer holiday. The substance sits in 2.6.13, which added tip-date file handling; the two after it are lint and bug fixes.
Development is fine-grained and test-driven — releases are small, numbered in tight sequence, and reported against a fixed NEW FEATURES / MINOR IMPROVEMENTS / BUG FIXES / DEPRECATED template with 100% code coverage tracked as a line item. The recent work concentrates on validating user-supplied input files rather than expanding BEAST2 model coverage, which suggests the model surface is considered largely done and the remaining friction is in what users feed it.
The pre-CRAN backlog should be squashed into a single CRAN submission once the release window reopens; further work is most likely more input-file validation in the same check_/read_ family.
sftime extends sf with an active time column, giving R a data frame class for data that is both spatial and temporal. Its recent history is almost entirely integration work: 0.3.0 added conversion methods from spatstat point patterns, sftrack and sftraj movement objects and cubble data frames, plus dedicated tidyr::drop_na() and dplyr::dplyr_reconstruct() methods. The two releases since are a namespace version-check correction and a switch from the magrittr pipe to the native pipe in examples.
The package's job is to be interoperable, so its releases follow whatever the surrounding spatial and tidyverse packages do. The dplyr_reconstruct() work is the clearest example of why that matters: inheriting sf's method caused column binding to silently return an sf object where an sftime object was expected, which is the kind of class-preservation bug that only surfaces two steps downstream. Development is sparse, roughly one release a year.
Expect further conversion methods as new spatiotemporal classes appear in the R spatial ecosystem, and continued tracking of dplyr and tidyr generics. The entries do not indicate any planned change to the sftime class itself.
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 beautier or sftime.
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 beautier alternatives → · See all sftime alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. beautier and sftime 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. beautier and sftime 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 beautier alternatives in Analytics are ranked by recent ship velocity. Browse the "beautier alternatives" section above for the current picks, or visit /alternatives/beautier for the full list with editorial commentary on each.
Top sftime alternatives in Analytics are ranked by recent ship velocity. Browse the "sftime alternatives" section above for the current picks, or visit /alternatives/sftime for the full list with editorial commentary on each.