tidytext
Finished, widely taught, and shipping roxygen fixes.
Comparison · Analytics
lubridate vs probably
A side-by-side editorial comparison of lubridate and probably — release velocity, themes, recent moves, and the top alternatives to consider.
lubridate vs probably: at a glance
What is lubridate?
lubridate ships parsing fixes, timezone-data churn, and a long-overdue MIT relicense.
lubridate is R's standard package for date-time manipulation. Recent releases are dominated by parsing correctness — partial datetimes, multiple format strings, month names colliding with the %a format — and by adapting to timezone database changes in R-devel. Version 1.9.5 also relicensed the package to MIT.
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.
lubridate vs probably: editorial side-by-side
lubridate
0.0ANALYTICS
lubridate ships parsing fixes, timezone-data churn, and a long-overdue MIT relicense.
◆ Current state
lubridate is R's standard package for date-time manipulation. Recent releases are dominated by parsing correctness — partial datetimes, multiple format strings, month names colliding with the %a format — and by adapting to timezone database changes in R-devel. Version 1.9.5 also relicensed the package to MIT.
◆ Where it's heading
The feature surface has been stable since 1.9.0 deprecated the roll argument for roll_dst and added integer coercion for Duration, Period and Interval. What continues is a steady stream of parsing edge cases and tzdata churn the package absorbs on its users' behalf, which is most of what a date-time library's maintenance actually is.
◆ Prediction
Expect further releases driven by tzdata and R-devel changes, with parsing fixes arriving as locale and format edge cases get reported.
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 lubridate 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 lubridate or probably.
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.
vetiver
Posit's MLOps package went quiet for two years, then came back to keep up with recipes.
patchwork
patchwork stopped being a ggplot composer and became a page composer.
See all lubridate alternatives → · See all probably alternatives →
Recent activity from lubridate and probably
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 6mo agolubridatelubridate 1.9.5 relicenses to MIT and fixes timestamp order
- 6mo agolubridatelubridate 1.9.4 parses partial datetimes like as.POSIXct()
- 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 ⚡
- 3y agolubridatelubridate 1.9.2 fixes month parsing when %a is present
- 3y agolubridatelubridate 1.9.1 accepts multiple formats in as_datetime()
- 3y agolubridatelubridate 1.9.0 replaces roll with an explicit roll_dst argument
- 5y agolubridatelubridate 1.7.10 fixes interval division across leap years
Frequently asked questions
What is the difference between lubridate and probably?
They serve adjacent needs but don't currently overlap on shipped themes. lubridate and probably are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is lubridate better than probably?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. lubridate and probably are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to lubridate?
Top lubridate alternatives in Analytics are ranked by recent ship velocity. Browse the "lubridate alternatives" section above for the current picks, or visit /alternatives/lubridate 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.