tidytext
Finished, widely taught, and shipping roxygen fixes.
A side-by-side editorial comparison of readxl and workflowsets — release velocity, themes, recent moves, and the top alternatives to consider.
readxl has shipped almost nothing but vendored-dependency upkeep since 2022.
readxl reads Excel files into R without requiring Excel, bundling the libxls and RapidXML C libraries. Four of its last six releases state outright that they contain no user-facing changes, existing instead to satisfy CRAN, silence a sanitizer warning, or re-embed a patched libxls.
workflowsets keeps widening what counts as a model worth comparing.
workflowsets holds a grid of preprocessor and model combinations and evaluates all of them under one call to workflow_map(). The releases in view widen that grid — clustering specifications via tidyclust, censored regression via an eval_time argument, case weights — and fill in the accessors around it with collect_notes(), collect_extracts() and fit_best(). The long-running pull_*() deprecation finally reached the error stage in 1.1.1.
readxl reads Excel files into R without requiring Excel, bundling the libxls and RapidXML C libraries. Four of its last six releases state outright that they contain no user-facing changes, existing instead to satisfy CRAN, silence a sanitizer warning, or re-embed a patched libxls.
The real work has become stewardship of vendored C code: absorbing libxls security fixes and keeping the package compiling across Alpine, UBSAN and successive cpp11 versions. 1.5.0 breaks the streak only slightly, with a network-drive permission warning fix and a cpp11 floor raised to dodge a segfault.
Expect the same rhythm — releases triggered by toolchain breakage or an upstream libxls patch rather than new spreadsheet-reading capability.
workflowsets holds a grid of preprocessor and model combinations and evaluates all of them under one call to workflow_map(). The releases in view widen that grid — clustering specifications via tidyclust, censored regression via an eval_time argument, case weights — and fill in the accessors around it with collect_notes(), collect_extracts() and fit_best(). The long-running pull_*() deprecation finally reached the error stage in 1.1.1.
The package's job is comparison, so its direction is set by what tidymodels can express: every time a new model paradigm lands elsewhere, workflowsets has to learn to rank it. Clustering was the largest of those steps because it has no outcome column to score against. Alongside that runs a slower cleanup — named-only optional arguments, type checking on inputs, informative errors when someone passes a workflow set to fit() — that reads as a package hardening after its API settled.
Expect the tailor postprocessors that workflows added in 1.3.0 to need representation here next, since a workflow set that cannot vary the postprocessor cannot compare calibration choices.
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 readxl or workflowsets.
Finished, widely taught, and shipping roxygen fixes.
Text features finally stay sparse all the way to the model.
The package that made calibration a step instead of an afterthought.
The tidymodels pipeline grew a third stage, and it happens after the model runs.
Posit's MLOps package went quiet for two years, then came back to keep up with recipes.
patchwork stopped being a ggplot composer and became a page composer.
See all readxl alternatives → · See all workflowsets alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. readxl and workflowsets 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. readxl and workflowsets 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.
Top readxl alternatives in Analytics are ranked by recent ship velocity. Browse the "readxl alternatives" section above for the current picks, or visit /alternatives/readxl for the full list with editorial commentary on each.
Top workflowsets alternatives in Analytics are ranked by recent ship velocity. Browse the "workflowsets alternatives" section above for the current picks, or visit /alternatives/workflowsets for the full list with editorial commentary on each.