tidytext
Finished, widely taught, and shipping roxygen fixes.
A side-by-side editorial comparison of dbplyr and mlr3mbo — 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.
mlr3mbo picked its defaults from a benchmark study, not from taste
mlr3mbo does model-based and Bayesian optimisation for mlr3. Its 1.0.0 release added a dictionary of pre-built acquisition-function optimisers and, more consequentially, replaced the default surrogate, acquisition function and optimiser settings with values derived from a large-scale benchmark study. The releases since are corrections to the acquisition-optimiser path exposed by that new default configuration.
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.
mlr3mbo does model-based and Bayesian optimisation for mlr3. Its 1.0.0 release added a dictionary of pre-built acquisition-function optimisers and, more consequentially, replaced the default surrogate, acquisition function and optimiser settings with values derived from a large-scale benchmark study. The releases since are corrections to the acquisition-optimiser path exposed by that new default configuration.
The package has moved from a toolkit that expected users to assemble a Bayesian optimisation loop into one with a defensible default loop, and the recent fixes — warm-start sizing on multi-objective archives, silently discarded terminators, stale x_domain values — are the consequences of more people running the default path.
Expect continued hardening of the acquisition-optimiser classes rather than new acquisition functions.
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 mlr3mbo.
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 mlr3mbo alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. mlr3mbo 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. mlr3mbo 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 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 mlr3mbo alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3mbo alternatives" section above for the current picks, or visit /alternatives/mlr3mbo for the full list with editorial commentary on each.