textrecipes
Text features finally stay sparse all the way to the model.
A side-by-side editorial comparison of Displayr and tidytext — release velocity, themes, recent moves, and the top alternatives to consider.
Chat is being made legible while the survey-analysis core picks up the fundamentals it lacked.
Displayr is shipping on two fronts at a steady, unhurried cadence. The AI assistant is being made auditable rather than more capable — a context pill showing exactly what a prompt will send, a change summary listing every item Chat added, edited or deleted, and an Explain This button that routes errors and warnings into Chat with context attached. Separately the document core is filling in fundamentals: controls that stay synced across pages and page masters, rolling averages computed on date-keyed tables, browser-style back and forward navigation, and templates that can be saved as folder-scoped defaults.
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.
Displayr is shipping on two fronts at a steady, unhurried cadence. The AI assistant is being made auditable rather than more capable — a context pill showing exactly what a prompt will send, a change summary listing every item Chat added, edited or deleted, and an Explain This button that routes errors and warnings into Chat with context attached. Separately the document core is filling in fundamentals: controls that stay synced across pages and page masters, rolling averages computed on date-keyed tables, browser-style back and forward navigation, and templates that can be saved as folder-scoped defaults.
The Chat work reads as a deliberate answer to the trust problem with AI in analyst tools — every release makes what the assistant touched inspectable rather than expanding what it can do unprompted. The other track is closing gaps a long-standing survey analysis platform accumulates, with the default-template mechanic notable for scoping defaults by Cloud Drive folder, which turns a personal preference into an organizational standard. Neither track has produced a directional move in this window.
Expect the transparency pattern to extend to Chat actions that modify data rather than layout, since the change summary establishes the mechanism. Folder-scoped defaults look like the start of broader template governance.
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 Displayr 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 Displayr 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. Displayr is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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. Displayr is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top Displayr alternatives in Analytics are ranked by recent ship velocity. Browse the "Displayr alternatives" section above for the current picks, or visit /alternatives/displayr 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.