tidytext
Finished, widely taught, and shipping roxygen fixes.
A side-by-side editorial comparison of dbplyr and mlr3measures — release velocity, themes, recent moves, and the top alternatives to consider.
dbplyr ends its two-year backend migration by dropping 1st edition support outright
dbplyr translates dplyr code into SQL, and 2.6.0 closes a migration that has been running since 2023: first-edition backends no longer work at all. The same release converts a long list of soft deprecations into hard failures and removes functions deprecated as far back as 2019. The releases before it were translation-quality work across SQL Server, Redshift, Snowflake, Postgres, Spark and Teradata.
mlr3measures is systematically retrofitting sample weights across every metric
mlr3measures is the metric library behind mlr3. Recent releases follow two threads: adding measures — linex, pinball, Mu AUC, gmean, gpr, mcc — and retrofitting sample_weights support across the existing ones, reaching AUC and the confusion-matrix family in 1.3.0. Along the way 1.1.0 deprecated four regression measures and corrected the bias definitions.
dbplyr translates dplyr code into SQL, and 2.6.0 closes a migration that has been running since 2023: first-edition backends no longer work at all. The same release converts a long list of soft deprecations into hard failures and removes functions deprecated as far back as 2019. The releases before it were translation-quality work across SQL Server, Redshift, Snowflake, Postgres, Spark and Teradata.
The package is trading compatibility surface for a smaller, more consistent core it can actually evolve — qualified table names were overhauled in 2.5.0, sql() and ident() were refactored internally, and the cte argument gave way to a single sql_options() entry point. Backend breadth keeps growing at the translation level even as the extension API narrows.
With the edition split finally gone, expect the next cycle to spend its budget on dialect translations and the newer Spark/Databricks path rather than on further deprecation.
mlr3measures is the metric library behind mlr3. Recent releases follow two threads: adding measures — linex, pinball, Mu AUC, gmean, gpr, mcc — and retrofitting sample_weights support across the existing ones, reaching AUC and the confusion-matrix family in 1.3.0. Along the way 1.1.0 deprecated four regression measures and corrected the bias definitions.
The library is maturing rather than growing: weighted evaluation and observation-wise loss functions are being brought to metrics that already existed, which is what downstream weighted-resampling and per-observation analysis need. The deprecations suggest the maintainers are willing to remove measures they consider ill-defined rather than keep them for compatibility.
Expect sample_weights and observation-wise variants to reach the remaining measures that lack them.
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 dbplyr or mlr3measures.
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 dbplyr alternatives → · See all mlr3measures alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dbplyr and mlr3measures 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. dbplyr and mlr3measures 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 dbplyr alternatives in Analytics are ranked by recent ship velocity. Browse the "dbplyr alternatives" section above for the current picks, or visit /alternatives/dbplyr for the full list with editorial commentary on each.
Top mlr3measures alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3measures alternatives" section above for the current picks, or visit /alternatives/mlr3measures for the full list with editorial commentary on each.