mrbayes
mrbayes spent 2026 auditing its own Bayesian MR estimators for coding errors.
A side-by-side editorial comparison of fastplyr and modeltime.resample — release velocity, themes, recent moves, and the top alternatives to consider.
A fast dplyr stand-in that keeps finding new places to skip work entirely.
fastplyr reimplements the dplyr verbs on a faster backend, exposing f_summarise, f_mutate, f_reframe and a set of group metadata helpers alongside optimized joins and quantiles. The most recent release removes non-API C functions and raises the floor to R 4.5.0, a steep requirement that follows the C++17 requirement introduced a release earlier. The verb surface itself has been stable since 0.9.0.
modeltime.resample exists to keep backtesting working as tidymodels shifts underneath it.
modeltime.resample runs time series cross-validation over modeltime models, returning per-resample predictions and accuracy plots. Version 0.3.0 is the substantive release in view: tune 2.0.0 compatibility, deterministic seeding via withr, guaranteed .predictions output, and clearer failures when resample fits break. The three releases before it are dependency chores.
fastplyr reimplements the dplyr verbs on a faster backend, exposing f_summarise, f_mutate, f_reframe and a set of group metadata helpers alongside optimized joins and quantiles. The most recent release removes non-API C functions and raises the floor to R 4.5.0, a steep requirement that follows the C++17 requirement introduced a release earlier. The verb surface itself has been stable since 0.9.0.
The optimization strategy has shifted from making individual functions fast to reasoning about expressions before evaluating them — 0.9.9 began marking simple operators as group-unaware so expressions built only from them are evaluated across the whole data frame rather than per group. That is a structural bet: the package increasingly inspects what you wrote to decide how much work is actually needed. Running alongside it is a steady tightening of build requirements, with C++17, R 4.5.0 and CRAN's C API rules all landing within a year.
Expect the group-unaware classification to widen to more functions, since each addition compounds across every grouped expression, and expect the dependency floors to keep rising as the package tracks CRAN's compiled-code policy.
modeltime.resample runs time series cross-validation over modeltime models, returning per-resample predictions and accuracy plots. Version 0.3.0 is the substantive release in view: tune 2.0.0 compatibility, deterministic seeding via withr, guaranteed .predictions output, and clearer failures when resample fits break. The three releases before it are dependency chores.
Every entry here is compatibility work against something upstream — hardhat 1.0.0, workflows regression mode, then tune 2.0.0 twice. The 0.3.0 notes show a second concern emerging alongside it: making failures legible, with .notes on failed fits, actionable errors from unnest_modeltime_resamples(), and fallback logic when prediction columns go missing across versions. Reproducibility gets the same treatment through explicit seeding.
Expect the next release to track the next tidymodels breaking change, with any new work continuing on error reporting rather than resampling strategies.
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 fastplyr or modeltime.resample.
mrbayes spent 2026 auditing its own Bayesian MR estimators for coding errors.
lineup2 ships once every few years, and 2026's release is a logo and a core-count tweak.
stringi has spent two years on build hardening since its Unicode 15.1 reset.
A 2017 chemometrics method frozen in place, visited only when CRAN changes its documentation rules.
Belgium's invasive-species indicator toolkit is in steady refinement, one plotting edge case at a time.
The ICES stock assessment client took upload away in 2024 and spent two years giving it back.
See all fastplyr alternatives → · See all modeltime.resample alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. fastplyr and modeltime.resample 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. fastplyr and modeltime.resample 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 fastplyr alternatives in Analytics are ranked by recent ship velocity. Browse the "fastplyr alternatives" section above for the current picks, or visit /alternatives/fastplyr for the full list with editorial commentary on each.
Top modeltime.resample alternatives in Analytics are ranked by recent ship velocity. Browse the "modeltime.resample alternatives" section above for the current picks, or visit /alternatives/modeltime-resample for the full list with editorial commentary on each.