FoRecoML
The machine-learning arm of a forecast reconciliation toolkit, four months old and already sharing its sibling's plumbing.
A side-by-side editorial comparison of Databricks and eratosthenes — 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.
eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.
eratosthenes does Bayesian estimation of archaeological chronologies from relative sequences, absolute constraints and artifact assemblages. The 0.0.9 line built out the inference diagnostics — traceplots, histograms, batch-means MCSE reporting, displacement estimation — and then consolidated artifact probability-density estimation into a single gibbs_ad_type(). The 0.1.0 tag turns outward instead, adding validators for every user-supplied structure and replacing seq_check() with a more informative seq_diag().
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.
eratosthenes does Bayesian estimation of archaeological chronologies from relative sequences, absolute constraints and artifact assemblages. The 0.0.9 line built out the inference diagnostics — traceplots, histograms, batch-means MCSE reporting, displacement estimation — and then consolidated artifact probability-density estimation into a single gibbs_ad_type(). The 0.1.0 tag turns outward instead, adding validators for every user-supplied structure and replacing seq_check() with a more informative seq_diag().
The package is moving from research code to something a non-author can run. Consolidating estimation behind one function, then wrapping every input class in a validator, are the two steps that make failures legible instead of cryptic, and the diagnostics added earlier serve the same end for the sampler itself. Nothing in the window changes the underlying model; the work is all about making it usable and its output checkable.
With inputs validated and diagnostics in place, the next release is more likely to extend the constraint or assemblage modelling than to keep reworking the interface, though the feed's three sparse tags give little to read a cadence from.
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 eratosthenes.
The machine-learning arm of a forecast reconciliation toolkit, four months old and already sharing its sibling's plumbing.
Forecast reconciliation with a real object model, five years after it started returning bare matrices.
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.
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
See all Databricks alternatives → · See all eratosthenes 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 eratosthenes alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "eratosthenes alternatives" section above for the current picks, or visit /alternatives/eratosthenes for the full list with editorial commentary on each.