ManageEngine RecoveryManager Plus
RecoveryManager Plus keeps widening its backup coverage across the Microsoft identity estate.
A side-by-side editorial comparison of mlr3cmprsk and TimescaleDB — release velocity, themes, recent moves, and the top alternatives to consider.
Competing risks arrive in mlr3, going from a non-parametric baseline to Fine-Gray regression in seven weeks.
mlr3cmprsk extends mlr3 to competing-risks analysis: learners predicting cumulative incidence functions, plus measures to score them. It appeared in February 2026 and reached 0.0.5 by April, adding a Fine-Gray learner and a Brier score along the way. The version numbers say pre-release; the cadence says active build-out.
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.
mlr3cmprsk extends mlr3 to competing-risks analysis: learners predicting cumulative incidence functions, plus measures to score them. It appeared in February 2026 and reached 0.0.5 by April, adding a Fine-Gray learner and a Brier score along the way. The version numbers say pre-release; the cadence says active build-out.
The package assembled a working evaluation stack fast. It started with the Aalen-Johansen estimator as a non-parametric baseline, added Fine-Gray as a regression alternative, then filled in the scoring side with an AUC refactor and a fixed-time Brier score. Development has run in lockstep with survdistr and mlr3extralearners, which picked up the dependency at 1.5.2.
The visible gaps are more learners — cause-specific Cox and boosting variants — and the tuning and pipeline integration the rest of mlr3 expects; the measure side currently looks further along than the model side.
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 mlr3cmprsk or TimescaleDB.
RecoveryManager Plus keeps widening its backup coverage across the Microsoft identity estate.
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.
See all mlr3cmprsk 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 mlr3cmprsk alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3cmprsk alternatives" section above for the current picks, or visit /alternatives/mlr3cmprsk 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.