Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of mlr3learners and TimescaleDB — release velocity, themes, recent moves, and the top alternatives to consider.
mlr3learners spends its releases absorbing upstream churn
mlr3learners wraps the standard model packages — ranger, xgboost, glmnet, kknn — for mlr3. Its recent history is dominated by upstream events rather than its own plans: kknn was pulled from CRAN and its learners removed in 0.11.0, then restored in 0.12.0 when the package returned. The newest release absorbs glmnet 5.0 while adding a predict_raw flag across all learners and probit support to logistic regression.
TimescaleDB is paying down correctness debt in its columnstore query paths.
The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.
mlr3learners wraps the standard model packages — ranger, xgboost, glmnet, kknn — for mlr3. Its recent history is dominated by upstream events rather than its own plans: kknn was pulled from CRAN and its learners removed in 0.11.0, then restored in 0.12.0 when the package returned. The newest release absorbs glmnet 5.0 while adding a predict_raw flag across all learners and probit support to logistic regression.
The package's job is insulation, and the changelog shows what that costs — compatibility-only releases interleaved with small capability additions that expose more of each upstream model. The direction of travel is toward giving users access to the raw upstream objects rather than hiding them.
Expect the next release to track another upstream version bump, with incremental exposure of learner-specific fields continuing alongside.
The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.
The feature work of 2.27 and 2.28 - vectorized filter evaluation, first/last derived straight from columnstore batch metadata, sparse indexes, SkipScan on compressed data - has been followed by a steady stream of fixes to those same code paths. 2.29.2 alone repairs SkipScan dropping uncompressed rows, sparse-index pushdown returning wrong results for IS NULL, and gapfill over window aggregates. That is the normal cost of pushing query optimizations into a compressed columnar store, and the project is working through it release by release rather than pausing.
With three consecutive patch releases on the 2.29 line and no new highlighted features since 2.29.0, the next minor is likely to resume the columnstore performance work - though the density of wrong-results fixes suggests more patches first.
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 mlr3learners or TimescaleDB.
Omni ships weekly, and almost every week the headline item is an AI feature.
silx settles into maintenance a release after its PySide6 migration
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
aniread stops asking you to know which tracker wrote the file
Rho's release machinery finally produced a stable build — and it shipped no new product.
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
See all mlr3learners alternatives → · See all TimescaleDB alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. TimescaleDB is currently shipping more aggressively (velocity 5.0 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. TimescaleDB is currently shipping more aggressively (velocity 5.0 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 mlr3learners alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3learners alternatives" section above for the current picks, or visit /alternatives/mlr3learners for the full list with editorial commentary on each.
Top TimescaleDB alternatives in Analytics are ranked by recent ship velocity. Browse the "TimescaleDB alternatives" section above for the current picks, or visit /alternatives/timescaledb for the full list with editorial commentary on each.