datefixR
The messy-date parser rewrote its core in Rust and came out 300x faster.
A side-by-side editorial comparison of mirai and sftime — release velocity, themes, recent moves, and the top alternatives to consider.
mirai removed its dispatcher process and added memory backpressure to the queue.
The async evaluation framework releases roughly monthly and moves fast at the architecture level. In 2.7.0 the dispatcher stopped being a separate process and became a thread, after its loop had already been rewritten in C inside nanonext one release earlier. The same release added an opt-in memory budget for queued task payloads and try_mirai(), which returns NULL immediately rather than blocking when that budget is exhausted.
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.
The async evaluation framework releases roughly monthly and moves fast at the architecture level. In 2.7.0 the dispatcher stopped being a separate process and became a thread, after its loop had already been rewritten in C inside nanonext one release earlier. The same release added an opt-in memory budget for queued task payloads and try_mirai(), which returns NULL immediately rather than blocking when that budget is exhausted.
Two threads of work run together: cutting overhead out of the task path — thread-based dispatcher, in-process transport for synchronous daemons, lower per-element dispatch cost in mirai_map() — and making the framework safe to embed in an event loop, where blocking the host R thread is not acceptable. Deployment reach is growing too, with http_config() launching remote daemons over HTTP APIs and auto-configuring for Posit Workbench. Each release pins a minimum nanonext version, so the two packages advance as one unit.
With backpressure in place but opt-in, the open question these notes leave is whether a default memory budget arrives; continued overhead reduction and Shiny-facing non-blocking paths are the safer bet.
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 mirai 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 mirai alternatives → · See all sftime alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. mirai 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mirai 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.
Top mirai alternatives in Analytics are ranked by recent ship velocity. Browse the "mirai alternatives" section above for the current picks, or visit /alternatives/mirai 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.