stacks
Model stacking in tidymodels, quietly migrating off foreach and onto future
Comparison · Analytics
Delta Lake vs probably
A side-by-side editorial comparison of Delta Lake and probably — release velocity, themes, recent moves, and the top alternatives to consider.
Delta Lake vs probably: at a glance
What is Delta Lake?
Delta Lake's public releases are patch work while Databricks kernel builds fill the feed.
Two kinds of entry dominate: numbered patch releases on the 3.3 and 4.3 lines, and near-daily Databricks kernel build tags that carry a single commit message each. The patch releases are targeted correctness work — a metadata cleanup that could delete transaction log files still needed to reconstruct versions inside the retention window, a Delta Sharing cache refresh that dropped deletion-vector URL mappings, an OAuth key-casing bug in the REST Catalog, and S3A fast-listing through FilterFileSystem wrappers. The 3.3.3 release also declines to publish delta-iceberg, leaving UniForm users on the prior patch.
What is probably?
The package that made calibration a step instead of an afterthought.
probably started as a small utility for class predictions and equivocal zones, and version 1.0.0 turned it into tidymodels' calibration and uncertainty package: cal_plot_*, cal_estimate_*, cal_validate_* and cal_apply across binary, multiclass and regression problems, plus conformal prediction intervals. Since then the work has been consolidation — a large internal refactor with no API change, split conformal and conformal quantile regression, bound_prediction(), and required_pkgs() and butcher methods so conformal objects can be deployed and stripped.
Delta Lake vs probably: editorial side-by-side
Delta Lake
5.0ANALYTICS
Delta Lake's public releases are patch work while Databricks kernel builds fill the feed.
◆ Current state
Two kinds of entry dominate: numbered patch releases on the 3.3 and 4.3 lines, and near-daily Databricks kernel build tags that carry a single commit message each. The patch releases are targeted correctness work — a metadata cleanup that could delete transaction log files still needed to reconstruct versions inside the retention window, a Delta Sharing cache refresh that dropped deletion-vector URL mappings, an OAuth key-casing bug in the REST Catalog, and S3A fast-listing through FilterFileSystem wrappers. The 3.3.3 release also declines to publish delta-iceberg, leaving UniForm users on the prior patch.
◆ Where it's heading
The project is stabilising two supported lines in parallel rather than moving the format forward in these entries, and the recurring theme is metadata and log durability — the parts of Delta that silently break time travel and CDF when they are wrong. Kernel work continues in the build tags, most visibly treating _last_checkpoint as opaque JSON. The unpublished UniForm artifact is the one open thread with a stated follow-up plan.
◆ Prediction
A follow-up patch that restores the delta-iceberg artifact for the 3.3 line is the clearest next step; otherwise expect the kernel build cadence to continue between numbered releases.
probably
0.0ANALYTICS
The package that made calibration a step instead of an afterthought.
◆ Current state
probably started as a small utility for class predictions and equivocal zones, and version 1.0.0 turned it into tidymodels' calibration and uncertainty package: cal_plot_*, cal_estimate_*, cal_validate_* and cal_apply across binary, multiclass and regression problems, plus conformal prediction intervals. Since then the work has been consolidation — a large internal refactor with no API change, split conformal and conformal quantile regression, bound_prediction(), and required_pkgs() and butcher methods so conformal objects can be deployed and stripped.
◆ Where it's heading
The recent releases are about making these objects survive leaving the session. butcher and required_pkgs() methods are what a model needs to be pinned, containerised and served, and their arrival alongside workflows adding a tailor postprocessing stage and vetiver adding probably support points the same way: calibration is being moved out of analysis scripts and into the deployed pipeline. The cal_*_none() reference implementations are the tell that calibration is now something people tune rather than apply once.
◆ Prediction
Expect the calibration functions to be reachable directly from a tuned workflow's postprocessing stage rather than applied to predictions afterwards, following the tailor integration that workflows just shipped.
Alternatives to Delta Lake and probably
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 Delta Lake or probably.
modeldata
The tidymodels example-data package grows one dataset at a time, on nobody's schedule
tidytext
Finished, widely taught, and shipping roxygen fixes.
textrecipes
Text features finally stay sparse all the way to the model.
workflowsets
workflowsets keeps widening what counts as a model worth comparing.
workflows
The tidymodels pipeline grew a third stage, and it happens after the model runs.
See all Delta Lake alternatives → · See all probably alternatives →
Recent activity from Delta Lake and probably
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 21h agoDelta LakeLog-retention and Delta Sharing cache fixes; UniForm jar not published
- 13d agoDelta LakeDatabricks kernel build tag (2026-07-30)
- 1mo agoDelta LakeKernel build tag: _last_checkpoint captured as opaque JSON
- 1mo agoDelta LakeDelta Lake 4.3.1
- 1mo agoDelta LakeDatabricks kernel build tag (2026-07-07)
- 1mo agoDelta LakeDatabricks kernel build tag, DBI variant (2026-07-06)
- 10mo agoprobablyConformal objects gain required_pkgs() and butcher methods
- 1y agoprobablyggplot2 test updates and a clearer validation-set error
- 1y agoprobablyCalibration internals refactored; isotonic bootstrap bug fixed
- 2y agoprobablyFix grouping sensitivity to variable type
- 3y agoprobablySplit conformal and conformal quantile regression added
- 3y agoprobablyCalibration and conformal inference arrive in tidymodels ⚡
Frequently asked questions
What is the difference between Delta Lake and probably?
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.
Is Delta Lake better than probably?
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.
What are the best alternatives to Delta Lake?
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.
What are the best alternatives to probably?
Top probably alternatives in Analytics are ranked by recent ship velocity. Browse the "probably alternatives" section above for the current picks, or visit /alternatives/probably for the full list with editorial commentary on each.