← Back to home
Comparison · Analytics

textrecipes vs workflowsets

A side-by-side editorial comparison of textrecipes and workflowsets — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:tidymodels

textrecipes vs workflowsets: at a glance

Featuretextrecipesworkflowsets
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themestext-processing, tidymodels, recipes, sparse-datatidymodels, model-comparison, clustering, tuning
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is textrecipes?

Text features finally stay sparse all the way to the model.

textrecipes supplies the recipes steps for turning text into model-ready columns: tokenizing, hashing, term frequency, TF-IDF, and word embeddings. Version 1.1.0 added a sparse argument to step_dummy_hash(), step_texthash(), step_tf() and step_tfidf() so they emit sparse vectors. The releases before it are a long consistency pass — keep_original_cols on every step that creates columns, informative errors on name collisions, tunable arguments documented, integer rather than double output where integers are what is meant.

Read the full textrecipes trajectory →

What is workflowsets?

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.

Read the full workflowsets trajectory →

textrecipes vs workflowsets: editorial side-by-side

T
textrecipes
ANALYTICS
0.0

Text features finally stay sparse all the way to the model.

◆ Current state

textrecipes supplies the recipes steps for turning text into model-ready columns: tokenizing, hashing, term frequency, TF-IDF, and word embeddings. Version 1.1.0 added a sparse argument to step_dummy_hash(), step_texthash(), step_tf() and step_tfidf() so they emit sparse vectors. The releases before it are a long consistency pass — keep_original_cols on every step that creates columns, informative errors on name collisions, tunable arguments documented, integer rather than double output where integers are what is meant.

◆ Where it's heading

Two forces drive this package. One is memory: text produces wide, mostly-zero matrices, and the sparse work is the direct answer, landing in the same period that workflows learned to fit and predict on dgCMatrix input. The other is upstream churn — the tweets tokenizer was deprecated because tokenizers deprecated it, the politeness feature disappeared when textfeatures left Suggests. The package's own agenda is consistency; its release timing belongs to its dependencies.

◆ Prediction

Expect the sparse argument to spread to the remaining column-producing steps, since only four of them have it, and expect more steps to be reworked as recipes' own sparse-data support matures.

W
workflowsets
ANALYTICS
0.0

workflowsets keeps widening what counts as a model worth comparing.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to textrecipes and workflowsets

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 textrecipes or workflowsets.

See all textrecipes alternatives → · See all workflowsets alternatives →

Recent activity from textrecipes and workflowsets

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1y agoworkflowsetscollect_extracts() added; pull_*() functions now error
  2. 1y agotextrecipesHashing and TF-IDF steps can emit sparse vectors
  3. 1y agotextrecipesstep_textfeatures() sped up; clean_levels NA bug fixed
  4. 2y agoworkflowsetsCensored regression evaluation; eval_time breaks positional args
  5. 2y agotextrecipestextfeatures dependency dropped; politeness feature removed
  6. 2y agotextrecipesuntokenize and normalization return factors
  7. 2y agotextrecipeskeep_original_cols everywhere; hashing column order fixed
  8. 3y agotextrecipesTunable arguments documented; name collisions now error
  9. 3y agoworkflowsetsClustering models enter workflow sets via tidyclust
  10. 4y agoworkflowsetsCase weights supported across a workflow set
  11. 4y agoworkflowsetsUpdate models and recipes across a set; mixed inputs accepted
  12. 5y agoworkflowsetsextract_*() supersedes pull_*() across tidymodels

Frequently asked questions

What is the difference between textrecipes and workflowsets?

Both compete on the same themes — tidymodels — within Analytics. textrecipes 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.

Is textrecipes better than workflowsets?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. textrecipes 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.

What are the best alternatives to textrecipes?

Top textrecipes alternatives in Analytics are ranked by recent ship velocity. Browse the "textrecipes alternatives" section above for the current picks, or visit /alternatives/textrecipes for the full list with editorial commentary on each.

What are the best alternatives to workflowsets?

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.