Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of mutagen and TimescaleDB — release velocity, themes, recent moves, and the top alternatives to consider.
A young package porting Stata's egen row-wise helpers to the tidyverse, one function per release
mutagen provides row-wise column-generation helpers for R data frames in the spirit of Stata's egen — gen_rowmean(), gen_rowsum(), gen_rowsd(), gen_rownonmiss() and about a dozen siblings. It reached 0.5.0 within three months of its first release, adding two or three functions each time. The most recent release adds gen_coldiff() and renames two functions to fit the naming scheme.
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.
mutagen provides row-wise column-generation helpers for R data frames in the spirit of Stata's egen — gen_rowmean(), gen_rowsum(), gen_rowsd(), gen_rownonmiss() and about a dozen siblings. It reached 0.5.0 within three months of its first release, adding two or three functions each time. The most recent release adds gen_coldiff() and renames two functions to fit the naming scheme.
The package is filling out a known surface rather than discovering one: the reference implementation exists in Stata, so development is a matter of working through the list. Alongside that, the naming convention is still settling — gen_rowmatch became gen_rowany, gen_percent became gen_colpercent, gen_na_listcol became gen_listcol_na — which is normal for a pre-1.0 package but means callers should expect further renames. Contributions are arriving from several first-time contributors.
The gen_col* prefix has only two members against a dozen gen_row* functions, so column-wise coverage is the obvious gap; expect it to fill before the naming stabilises for a 1.0.
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 mutagen 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 mutagen 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 mutagen alternatives in Analytics are ranked by recent ship velocity. Browse the "mutagen alternatives" section above for the current picks, or visit /alternatives/mutagen-r 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.