easystats
The easystats meta-package is install tooling wrapped around a relicensed ecosystem.
Comparison · Analytics
dtplyr vs tune
A side-by-side editorial comparison of dtplyr and tune — release velocity, themes, recent moves, and the top alternatives to consider.
dtplyr vs tune: at a glance
What is dtplyr?
dtplyr stopped hijacking data.table objects and became an opt-in translator
dtplyr converts dplyr and tidyr code into data.table syntax, and 1.3.0 redrew its boundary: verbs no longer dispatch to dtplyr translations just because dtplyr is loaded, so lazy_dt() has to be called explicitly. Since then the work has been translation coverage — reframe(), case_match(), consecutive_id() — plus a long tail of correctness fixes in grouping and .by.
What is tune?
tune extends tuning past the model itself to postprocessors, and adds a second parallel backend
tune runs hyperparameter search for tidymodels. Version 2.0.0 rewrote tune_grid() to make postprocessing tunable alongside preprocessing and the model, changed the .config naming scheme to match, and added mirai as a parallel backend next to future. Version 2.1.0 followed with quantile regression support and a replacement Gaussian process engine.
dtplyr vs tune: editorial side-by-side
dtplyr
0.0ANALYTICS
dtplyr stopped hijacking data.table objects and became an opt-in translator
◆ Current state
dtplyr converts dplyr and tidyr code into data.table syntax, and 1.3.0 redrew its boundary: verbs no longer dispatch to dtplyr translations just because dtplyr is loaded, so lazy_dt() has to be called explicitly. Since then the work has been translation coverage — reframe(), case_match(), consecutive_id() — plus a long tail of correctness fixes in grouping and .by.
◆ Where it's heading
The package is trailing dplyr's own feature releases rather than leading them, adding each new verb once it settles upstream. Performance work is targeted at specific verbs where data.table has a faster primitive: setorder() for arrange(), reference drops for select(), rleid() for consecutive_id(). Release cadence has thinned considerably since 2023.
◆ Prediction
Expect further one-for-one translations as dplyr adds verbs, and continued fixes around .by and non-standard column names; the entries show no sign of a broader redesign.
tune
0.0ANALYTICS
tune extends tuning past the model itself to postprocessors, and adds a second parallel backend
◆ Current state
tune runs hyperparameter search for tidymodels. Version 2.0.0 rewrote tune_grid() to make postprocessing tunable alongside preprocessing and the model, changed the .config naming scheme to match, and added mirai as a parallel backend next to future. Version 2.1.0 followed with quantile regression support and a replacement Gaussian process engine.
◆ Where it's heading
Two migrations run through this timeline. The tunable surface keeps widening - first censored regression as a mode, then postprocessors via tailor - so that a candidate is now a preprocessor, model and postprocessor triple rather than just a model. The parallel story has moved from foreach to future and now to mirai, each step deprecating the last. Neither is finished.
◆ Prediction
Expect the foreach path to be removed outright, and the postprocessing surface to grow as tailor gains more steps; the GauPro switch will likely need follow-up as its behavior differs from the old engine.
Alternatives to dtplyr and tune
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 dtplyr or tune.
discrim
discrim settled into a thin engine shim after handing its model definitions to parsnip.
dbparser
dbparser shed its database and CSV writers to become just a DrugBank parser.
desirability2
desirability2 is making multi-metric model selection a first-class tidymodels step.
crosstalk
crosstalk is frozen infrastructure: four releases in five years, mostly CRAN upkeep.
cmdstanr
cmdstanr keeps adding fast approximations beside full HMC, and fighting Windows toolchains.
Recent activity from dtplyr and tune
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agotuneQuantile regression tuning; Bayesian search moves to GauPro
- 9mo agotuneFixes int_pctl() with future parallelism on last_fit()
- 11mo agodtplyrreframe(), case_match() and consecutive_id() gain translations
- 11mo agotunePostprocessors become tunable; mirai joins future as a backend ⚡
- 11mo agotuneDevelopment snapshot re-enabling skipped tests
- 1y agotuneWarns on foreach parallelism; space-filling grids by default
- 2y agotuneFixes parallel tuning errors under multisession plans
- 3y agodtplyrcrayon dependency dropped
- 3y agodtplyrVerbs stop auto-dispatching; lazy_dt() now required ⚡
- 3y agodtplyrdtplyr 1.2.2
- 4y agodtplyrdtplyr 1.2.1
- 4y agodtplyrEight tidyr verbs gain data.table translations
Frequently asked questions
What is the difference between dtplyr and tune?
They serve adjacent needs but don't currently overlap on shipped themes. dtplyr and tune 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.
Is dtplyr better than tune?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dtplyr and tune 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.
What are the best alternatives to dtplyr?
Top dtplyr alternatives in Analytics are ranked by recent ship velocity. Browse the "dtplyr alternatives" section above for the current picks, or visit /alternatives/dtplyr for the full list with editorial commentary on each.
What are the best alternatives to tune?
Top tune alternatives in Analytics are ranked by recent ship velocity. Browse the "tune alternatives" section above for the current picks, or visit /alternatives/tune for the full list with editorial commentary on each.