tidytext
Finished, widely taught, and shipping roxygen fixes.
A side-by-side editorial comparison of dbt Core and loo — 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.
loo keeps rewriting the diagnostics Bayesian modellers read off model comparison
loo computes leave-one-out cross-validation and model comparison for Bayesian models in the Stan ecosystem. Two releases in this window changed what users actually read: 2.7.0 replaced the fixed Pareto-k thresholds with sample-size-dependent ones and dropped the middle category, and 2.10.0 reshaped loo_compare's output into a data.frame with new uncertainty columns. The releases between are diagnostic robustness fixes and moment-matching corrections.
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.
loo computes leave-one-out cross-validation and model comparison for Bayesian models in the Stan ecosystem. Two releases in this window changed what users actually read: 2.7.0 replaced the fixed Pareto-k thresholds with sample-size-dependent ones and dropped the middle category, and 2.10.0 reshaped loo_compare's output into a data.frame with new uncertainty columns. The releases between are diagnostic robustness fixes and moment-matching corrections.
The package is being brought in line with the current PSIS literature rather than extended with new features, and the practical effect is that the numbers practitioners quote in papers keep changing meaning. Work is increasingly delegated to posterior for shared computations, and the project has added contributor process, benchmarks and a published AI contribution policy.
Expect further work on comparison diagnostics — the p_worse and diag_* columns are new enough that their defaults and documentation will likely be revised next.
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 loo.
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 loo 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 2.5), 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 2.5), 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 loo alternatives in Analytics are ranked by recent ship velocity. Browse the "loo alternatives" section above for the current picks, or visit /alternatives/loo for the full list with editorial commentary on each.