wooldridge
A textbook data package whose whole job is to stay installable, and whose releases prove how much work that is.
A side-by-side editorial comparison of Databricks and nuggets — release velocity, themes, recent moves, and the top alternatives to consider.
Databricks lands DBR 18.2 GA on Spark 4.1; the 18.x line is the active story, older LTS pages are mostly doc refreshes.
The substantive shipping event in the window is Databricks Runtime 18.2 GA on May 4, the latest minor in a fast 18.x cadence on Spark 4.1.0 (18.0 in January, 18.1 in March, 18.2 Beta on April 8, GA on May 4). The rest of the recent feed is an April 13 documentation refresh that updated release notes for older LTS versions — 14.3, 15.4, 16.4, 17.3, 13.3 — without new shipping behind them.
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
nuggets searches for association rules, contrasts and other conditional patterns in the GUHA tradition, with a C++ core behind dig() and an interactive explore() app for reading results. Since the 2.0 rewrite of that core, every release has widened the same three surfaces: more pattern families to mine, more of explore() to inspect them in, and steady performance work underneath. The most recent tag optimises dig() on sparse crisp data with a sparse bit chain and adds clustering characteristics to explore() for association rules.
The substantive shipping event in the window is Databricks Runtime 18.2 GA on May 4, the latest minor in a fast 18.x cadence on Spark 4.1.0 (18.0 in January, 18.1 in March, 18.2 Beta on April 8, GA on May 4). The rest of the recent feed is an April 13 documentation refresh that updated release notes for older LTS versions — 14.3, 15.4, 16.4, 17.3, 13.3 — without new shipping behind them.
Databricks is pushing Spark 4.1 hard through the runtime line: JDK 21 default in 18.x, breaking changes around NULL preservation and partition columns, aggressive deprecation of older behaviors (input_file_name removal, AWS SDK v1 shading). The 18.x cadence is roughly one minor every six weeks, and 16.4 LTS is acting as the bridge for customers needing to migrate Scala 2.12 code to 2.13 before they can move to 17 or 18.
Expect an 18.x LTS designation later in 2026 once the line stabilizes, with continued behavioral hardening and more shaded dependency cleanup. Doc refreshes for older LTS versions — particularly 13.3 LTS, which is close to its August 2026 end-of-support — will likely keep landing as Databricks pushes customers up the runtime stack.
nuggets searches for association rules, contrasts and other conditional patterns in the GUHA tradition, with a C++ core behind dig() and an interactive explore() app for reading results. Since the 2.0 rewrite of that core, every release has widened the same three surfaces: more pattern families to mine, more of explore() to inspect them in, and steady performance work underneath. The most recent tag optimises dig() on sparse crisp data with a sparse bit chain and adds clustering characteristics to explore() for association rules.
Two forces are shaping the package. One is coverage: baseline, complement and paired-baseline contrasts, correlations, tautologies, ancestors and clustering have all been added as first-class dig_ or explore_ surfaces, so the same search engine now answers a widening set of questions. The other is weight — Shiny packages moved from Imports to Suggests, BH and RcppThread dropped, XSIMD updated, parse_condition() rewritten in C++ — which keeps a package with an interactive app from forcing that app's dependencies on every user. Deprecations are handled through lifecycle rather than removed abruptly.
Expect the sparse-data optimisation to extend from crisp to fuzzy data, and explore() to keep gaining tabs as each new pattern family lands, on the roughly six-week cadence the 2.2 line has held.
Other Infra & APIs 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 Databricks or nuggets.
A textbook data package whose whole job is to stay installable, and whose releases prove how much work that is.
A graph-centrality package that spent 2026 making its existing measures usable at scale, then went quiet.
A test-theory package that grew into a graphical-model toolkit, now spending its releases paying down the API debt that growth created.
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.
dqcheckr adds drift analysis, then removes the YAML a user had to hand-write.
See all Databricks alternatives → · See all nuggets alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Databricks is currently shipping more aggressively (velocity 5.0 vs 2.5), 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. Databricks is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Databricks alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Databricks alternatives" section above for the current picks, or visit /alternatives/databricks for the full list with editorial commentary on each.
Top nuggets alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "nuggets alternatives" section above for the current picks, or visit /alternatives/nuggets for the full list with editorial commentary on each.