Whatagraph
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
A side-by-side editorial comparison of ardlverse and Delta Lake — release velocity, themes, recent moves, and the top alternatives to consider.
An outside audit against Stata found seven errors in ardlverse's panel estimator, including regressions with no intercept.
A small R package for autoregressive distributed lag models, with only three releases on record. The first two were administrative — a CRAN version note and a Zenodo metadata update. The third, 2.0.0, is a correction release built entirely from an external audit of panel_ardl() against Stata's xtpmg, and it is the only entry here with substantive content.
A 4.4.0 tag appears, but the feed carries only its release plumbing
The newest entry is the commit that tagged 4.4.0 — a version.sbt bump plus a local Maven overwrite setting needed for cross-Spark publishing, and it states outright that there are no runtime behaviour changes. The 4.4.0 release notes themselves have not reached this feed, so what the minor version actually contains is not readable here. Behind it sit two patch releases doing targeted correctness work: 3.3.3 on transaction log retention and Delta Sharing cache, 4.3.1 on Delta REST Catalog OAuth and S3A listing, interleaved with near-daily Databricks kernel build tags.
A small R package for autoregressive distributed lag models, with only three releases on record. The first two were administrative — a CRAN version note and a Zenodo metadata update. The third, 2.0.0, is a correction release built entirely from an external audit of panel_ardl() against Stata's xtpmg, and it is the only entry here with substantive content.
The package's direction is now set by verification against an established reference implementation rather than by feature work. The seven fixes bring panel_ardl() into strict alignment with the original Pesaran, Shin and Smith framework, and the most serious of them is structural: internal regressions used lm.fit(), which unlike lm() does not append an intercept, so every short-run regression across the PMG, MG and DFE estimators was forced through the origin. Design matrices now carry a column of ones and DFE reconstructs the grand-mean intercept to match standard fixed-effects output.
Expect the next releases to extend the same audit approach to the remaining estimators, since a package that has been validated against xtpmg on one function invites the same question about the rest.
The newest entry is the commit that tagged 4.4.0 — a version.sbt bump plus a local Maven overwrite setting needed for cross-Spark publishing, and it states outright that there are no runtime behaviour changes. The 4.4.0 release notes themselves have not reached this feed, so what the minor version actually contains is not readable here. Behind it sit two patch releases doing targeted correctness work: 3.3.3 on transaction log retention and Delta Sharing cache, 4.3.1 on Delta REST Catalog OAuth and S3A listing, interleaved with near-daily Databricks kernel build tags.
The project keeps two supported lines stable in parallel while the format work happens elsewhere, and the durable theme across these patches is metadata and log correctness — the failures that silently break time travel and CDF rather than throwing. The 4.4.0 prep notes one thing worth watching: artifacts are now published across Spark 4.0, 4.1 and 4.2 stages, so the cross-Spark support matrix is widening even as the release content stays out of view.
The 4.4.0 release notes should follow this tag and reveal what the minor version carries; until they do the entries support no read on its direction. The unresolved delta-iceberg artifact gap on the 3.3 line still has no follow-up here.
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 ardlverse or Delta Lake.
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
Lightdash keeps handing authoring to outside agents and keeping the governed layer for itself.
distributions3 0.3.0 adds sample-based distributions and likelihood derivatives
Basedash keeps pushing its data out of the workspace — now to people without accounts
RStudio ships through release branches, and the notes are commit messages
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
See all ardlverse alternatives → · See all Delta Lake alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Delta Lake 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. Delta Lake 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 ardlverse alternatives in Analytics are ranked by recent ship velocity. Browse the "ardlverse alternatives" section above for the current picks, or visit /alternatives/ardlverse-r for the full list with editorial commentary on each.
Top Delta Lake alternatives in Analytics are ranked by recent ship velocity. Browse the "Delta Lake alternatives" section above for the current picks, or visit /alternatives/delta-lake for the full list with editorial commentary on each.