textrecipes
Text features finally stay sparse all the way to the model.
A side-by-side editorial comparison of embed and tidytext — release velocity, themes, recent moves, and the top alternatives to consider.
embed keeps adding encoding steps while shedding its deep-learning dependencies
embed supplies recipes steps that turn categorical predictors into numeric representations — likelihood encoding, UMAP projection, string-distance collapsing. The 1.1.x line made UMAP arguments tunable and moved keras and tensorflow out of hard dependencies; 1.2.0 added analytical likelihood encoding with partial pooling and retired step_feature_hash() in favor of textrecipes.
Finished, widely taught, and shipping roxygen fixes.
tidytext is the package that made unnest_tokens() and the tidy-data approach to text analysis standard, and it has reached the point where its releases contain nothing to announce. The last three are roxygen package anchors, alt text on vignette figures, and a single bug fix in one stm tidier. The most recent substantive changes were in 0.4.0 and 0.3.3 — stm tidiers for high FREX and lift words, a labels function for scale_x_reordered(), and support for tidying STM models that use content covariates.
embed supplies recipes steps that turn categorical predictors into numeric representations — likelihood encoding, UMAP projection, string-distance collapsing. The 1.1.x line made UMAP arguments tunable and moved keras and tensorflow out of hard dependencies; 1.2.0 added analytical likelihood encoding with partial pooling and retired step_feature_hash() in favor of textrecipes.
Two quiet directions run through these releases. One is making the steps tunable rather than fixed, so they participate properly in tidymodels grids. The other is boundary maintenance: heavy dependencies pushed to Suggests, overlapping steps handed to the package that owns them. Recent releases are thin and fix-driven.
Expect further consolidation with textrecipes over which package owns which encoding step, and continued upkeep against xgboost and uwot releases rather than new step families.
tidytext is the package that made unnest_tokens() and the tidy-data approach to text analysis standard, and it has reached the point where its releases contain nothing to announce. The last three are roxygen package anchors, alt text on vignette figures, and a single bug fix in one stm tidier. The most recent substantive changes were in 0.4.0 and 0.3.3 — stm tidiers for high FREX and lift words, a labels function for scale_x_reordered(), and support for tidying STM models that use content covariates.
The direction is stability, and the release triggers are external. quanteda releases force updates to the dfm tidiers, a Matrix release forces another, tokenizers deprecating its tweet tokenizer forces removal of the tweet-specific functions here, and CRAN's Rd anchor requirement produces a release of its own. Nothing in the recent stream suggests new capability is planned, and for a package this embedded in teaching material that is a defensible position rather than a problem.
The entries do not support predicting new features. The likely next release is another compatibility update prompted by quanteda, stm, or a CRAN documentation requirement.
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 embed or tidytext.
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.
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 embed alternatives → · See all tidytext alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. embed and tidytext 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. embed and tidytext 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 embed alternatives in Analytics are ranked by recent ship velocity. Browse the "embed alternatives" section above for the current picks, or visit /alternatives/embed for the full list with editorial commentary on each.
Top tidytext alternatives in Analytics are ranked by recent ship velocity. Browse the "tidytext alternatives" section above for the current picks, or visit /alternatives/tidytext for the full list with editorial commentary on each.