tidytext
Finished, widely taught, and shipping roxygen fixes.
A side-by-side editorial comparison of dtplyr and mlr3fselect — release velocity, themes, recent moves, and the top alternatives to consider.
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.
mlr3fselect turned feature selection into an asynchronous, distributable job
mlr3fselect runs feature selection for mlr3. The defining change in this window is 1.4.0, which introduced FSelectorAsync and the asynchronous instance classes, letting searches run without a synchronous batch loop. Around it sit ensemble feature selection work — fastVoteR ranking, embedded ensemble selection, result combination — and performance work on objective evaluation.
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.
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.
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.
mlr3fselect runs feature selection for mlr3. The defining change in this window is 1.4.0, which introduced FSelectorAsync and the asynchronous instance classes, letting searches run without a synchronous batch loop. Around it sit ensemble feature selection work — fastVoteR ranking, embedded ensemble selection, result combination — and performance work on objective evaluation.
Two threads run in parallel: scaling the search itself through async execution and the rush backend, and making ensemble selection results easier to analyse via Pareto fronts, knee points and now removal of empty result rows. The rush backward-compatibility shim was dropped in 1.6.0, so the async path is now the assumed one.
Expect the ensemble result API to keep gaining analysis helpers, with async execution treated as the default rather than an option.
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 mlr3fselect.
Finished, widely taught, and shipping roxygen fixes.
Text features finally stay sparse all the way to the model.
The package that made calibration a step instead of an afterthought.
workflowsets keeps widening what counts as a model worth comparing.
The tidymodels pipeline grew a third stage, and it happens after the model runs.
Posit's MLOps package went quiet for two years, then came back to keep up with recipes.
See all dtplyr alternatives → · See all mlr3fselect alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dtplyr and mlr3fselect 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. dtplyr and mlr3fselect 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 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.
Top mlr3fselect alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3fselect alternatives" section above for the current picks, or visit /alternatives/mlr3fselect for the full list with editorial commentary on each.