tidytext
Finished, widely taught, and shipping roxygen fixes.
A side-by-side editorial comparison of dbt Core and mlr3fselect — release velocity, themes, recent moves, and the top alternatives to consider.
dbt keeps three maintenance branches alive while Fusion 2.0 crosses into beta.
dbt-core is running two lines at once: a Python 1.x maintenance train across 1.10, 1.11 and 1.12, and the Rust Fusion 2.0 rewrite now in its first beta. The August 12 batch pushed the same deprecated-version warning into all three maintenance branches on one day, with the substantive work isolated to 1.12.1 (OpenTelemetry spans for node and hook execution) and 1.11.13 (deterministic unit-test resolution). Fusion is where the capability surface is actually widening.
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.
dbt-core is running two lines at once: a Python 1.x maintenance train across 1.10, 1.11 and 1.12, and the Rust Fusion 2.0 rewrite now in its first beta. The August 12 batch pushed the same deprecated-version warning into all three maintenance branches on one day, with the substantive work isolated to 1.12.1 (OpenTelemetry spans for node and hook execution) and 1.11.13 (deterministic unit-test resolution). Fusion is where the capability surface is actually widening.
The 1.x branches are converging on housekeeping — deprecation warnings, jsonschema definitions synced down from Fusion, parse-order determinism, adapter config recognition. That is the signature of a codebase being held stable rather than extended. Fusion 2.0 is absorbing the new work: catalog-free binding, a lint rule engine, node selection for lint and format, a self-hostable docs server.
Expect the maintenance branches to keep taking cross-branch warnings and adapter-config fixes while Fusion moves through further betas. The OpenTelemetry work in 1.12.1 is flag-gated behind --snowflake-projects-otel, which suggests tracing arrives unflagged in a later release.
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 dbt Core 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 dbt Core 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. dbt Core is currently shipping more aggressively (velocity 7.5 vs 0.0), with 1 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. dbt Core is currently shipping more aggressively (velocity 7.5 vs 0.0), with 1 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 dbt Core alternatives in Analytics are ranked by recent ship velocity. Browse the "dbt Core alternatives" section above for the current picks, or visit /alternatives/dbt-core 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.