animation
Contribution-driven maintenance on a package whose last structural change was magick support.
Comparison · Analytics
readxl vs tune
A side-by-side editorial comparison of readxl and tune — release velocity, themes, recent moves, and the top alternatives to consider.
readxl vs tune: at a glance
What is readxl?
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.
What is tune?
tune extends tuning past the model itself to postprocessors, and adds a second parallel backend
tune runs hyperparameter search for tidymodels. Version 2.0.0 rewrote tune_grid() to make postprocessing tunable alongside preprocessing and the model, changed the .config naming scheme to match, and added mirai as a parallel backend next to future. Version 2.1.0 followed with quantile regression support and a replacement Gaussian process engine.
readxl vs tune: editorial side-by-side
readxl
0.0ANALYTICS
readxl has shipped almost nothing but vendored-dependency upkeep since 2022.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
Expect the same rhythm — releases triggered by toolchain breakage or an upstream libxls patch rather than new spreadsheet-reading capability.
tune
0.0ANALYTICS
tune extends tuning past the model itself to postprocessors, and adds a second parallel backend
◆ Current state
tune runs hyperparameter search for tidymodels. Version 2.0.0 rewrote tune_grid() to make postprocessing tunable alongside preprocessing and the model, changed the .config naming scheme to match, and added mirai as a parallel backend next to future. Version 2.1.0 followed with quantile regression support and a replacement Gaussian process engine.
◆ Where it's heading
Two migrations run through this timeline. The tunable surface keeps widening - first censored regression as a mode, then postprocessors via tailor - so that a candidate is now a preprocessor, model and postprocessor triple rather than just a model. The parallel story has moved from foreach to future and now to mirai, each step deprecating the last. Neither is finished.
◆ Prediction
Expect the foreach path to be removed outright, and the postprocessing surface to grow as tailor gains more steps; the GauPro switch will likely need follow-up as its behavior differs from the old engine.
Alternatives to readxl and tune
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 tune.
pins
pins keeps adding a storage backend per release while retiring its original API
tsibble
tsibble shipped one release in five and a half years - the data structure is finished
yardstick
yardstick made fairness metrics a first-class part of tidymodels evaluation
leaflet
leaflet relicensed to MIT and finished migrating off R's retired spatial stack
ggpubr
ggpubr reached 1.0.0 with p-value formatting presets for specific journals
Recent activity from readxl and tune
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agoreadxlreadxl 1.5.0 stops false access-denied warnings on network drives
- 3mo agotuneQuantile regression tuning; Bayesian search moves to GauPro
- 9mo agotuneFixes int_pctl() with future parallelism on last_fit()
- 11mo agotunePostprocessors become tunable; mirai joins future as a backend ⚡
- 11mo agotuneDevelopment snapshot re-enabling skipped tests
- 1y agoreadxlreadxl 1.4.5 clears a gcc UBSAN warning
- 1y agoreadxlreadxl 1.4.4 embeds libxls 1.6.3 with vulnerability fixes
- 1y agotuneWarns on foreach parallelism; space-filling grids by default
- 2y agotuneFixes parallel tuning errors under multisession plans
- 3y agoreadxlreadxl 1.4.3 ships with no user-facing changes
- 3y agoreadxlreadxl 1.4.2 embeds a libxls build fixing CVE-2021-27836
- 3y agoreadxlreadxl 1.4.1 regenerates help files for valid HTML5
Frequently asked questions
What is the difference between readxl and tune?
They serve adjacent needs but don't currently overlap on shipped themes. readxl and tune 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 readxl better than tune?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. readxl and tune 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 readxl?
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.
What are the best alternatives to tune?
Top tune alternatives in Analytics are ranked by recent ship velocity. Browse the "tune alternatives" section above for the current picks, or visit /alternatives/tune for the full list with editorial commentary on each.