tidytext
Finished, widely taught, and shipping roxygen fixes.
A side-by-side editorial comparison of gutenbergr and workflows — release velocity, themes, recent moves, and the top alternatives to consider.
gutenbergr has been rebuilt around caching and mirror resilience
gutenbergr downloads Project Gutenberg texts into R. Its recent releases are a sustained reliability push driven largely by one contributor: a download cache with its own function family, mirror discovery with a known-good fallback, a User-Agent string identifying the client, and a section-marker helper. The newest releases are narrow compatibility and duplication fixes on top of that base.
The tidymodels pipeline grew a third stage, and it happens after the model runs.
workflows bundles a preprocessor and a model into one object that tidymodels can fit, tune and extract from. Version 1.3.0 added a post stage backed by the tailor package, wired through every generic a workflow supports — augment, tidy, tunable, tune_args, required_pkgs and parameter extraction. Version 1.2.0 added sparse data support so fit() and predict() accept dgCMatrix and sparse tibbles. Earlier releases in view are boundary tightening: erroring on unknown model modes, on trained recipes, and on silently ignored formula offsets.
gutenbergr downloads Project Gutenberg texts into R. Its recent releases are a sustained reliability push driven largely by one contributor: a download cache with its own function family, mirror discovery with a known-good fallback, a User-Agent string identifying the client, and a section-marker helper. The newest releases are narrow compatibility and duplication fixes on top of that base.
Development is aimed squarely at the failure modes of depending on a volunteer-run mirror network — cache locally, degrade gracefully when the mirror list cannot be parsed, and identify yourself politely to the servers. The version sequence in this feed is not monotonic, so recency here follows publication date rather than version number.
Further work should continue along the caching and mirror-handling line, with dataset refreshes as the Gutenberg catalogue changes.
workflows bundles a preprocessor and a model into one object that tidymodels can fit, tune and extract from. Version 1.3.0 added a post stage backed by the tailor package, wired through every generic a workflow supports — augment, tidy, tunable, tune_args, required_pkgs and parameter extraction. Version 1.2.0 added sparse data support so fit() and predict() accept dgCMatrix and sparse tibbles. Earlier releases in view are boundary tightening: erroring on unknown model modes, on trained recipes, and on silently ignored formula offsets.
The object is filling out into a complete pipeline description rather than a preprocessing-plus-model pair. Postprocessing is the structural addition — calibration and threshold selection were previously done by hand after prediction, outside anything tidymodels could tune or record — and the fact that it arrived integrated with tunable() and tune_args() rather than as a standalone step is the point. The rest of the arc is the steady tidymodels habit of converting silent guesses into errors.
Expect tailor postprocessors to spread through tune and workflowsets next, since the parameter and tuning generics were wired up first, and expect sparse support to extend to more engines after lightgbm.
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 gutenbergr or workflows.
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.
workflowsets keeps widening what counts as a model worth comparing.
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 gutenbergr alternatives → · See all workflows alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. gutenbergr and workflows 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. gutenbergr and workflows 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 gutenbergr alternatives in Analytics are ranked by recent ship velocity. Browse the "gutenbergr alternatives" section above for the current picks, or visit /alternatives/gutenbergr for the full list with editorial commentary on each.
Top workflows alternatives in Analytics are ranked by recent ship velocity. Browse the "workflows alternatives" section above for the current picks, or visit /alternatives/workflows-r for the full list with editorial commentary on each.