tidytext
Finished, widely taught, and shipping roxygen fixes.
Comparison · Analytics
embed vs lime
A side-by-side editorial comparison of embed and lime — release velocity, themes, recent moves, and the top alternatives to consider.
embed vs lime: at a glance
What is embed?
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.
What is lime?
lime survives on compatibility patches years after its research moment
lime brings local interpretable model-agnostic explanations to R. Its substantive development finished around 0.5.0 in 2019, which added argument pass-through to predict(), a gower_pow tuning knob and a batch of fixes. Since then there have been three releases: a namespace fix, a maintainer handover to Emil Hvitfeldt with general upkeep, and a patch to work across xgboost versions.
embed vs lime: editorial side-by-side
embed
0.0ANALYTICS
embed keeps adding encoding steps while shedding its deep-learning dependencies
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
lime
0.0ANALYTICS
lime survives on compatibility patches years after its research moment
◆ Current state
lime brings local interpretable model-agnostic explanations to R. Its substantive development finished around 0.5.0 in 2019, which added argument pass-through to predict(), a gower_pow tuning knob and a batch of fixes. Since then there have been three releases: a namespace fix, a maintainer handover to Emil Hvitfeldt with general upkeep, and a patch to work across xgboost versions.
◆ Where it's heading
The package is in custodial maintenance — kept installable and compatible with the model packages it explains, rather than developed. The 2022 handover is the most consequential entry in the window because it determined that the package would keep getting patches at all.
◆ Prediction
Expect the next release to be another compatibility fix triggered by an upstream model package, not new explanation methods.
Alternatives to embed and lime
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 lime.
textrecipes
Text features finally stay sparse all the way to the model.
probably
The package that made calibration a step instead of an afterthought.
workflowsets
workflowsets keeps widening what counts as a model worth comparing.
workflows
The tidymodels pipeline grew a third stage, and it happens after the model runs.
vetiver
Posit's MLOps package went quiet for two years, then came back to keep up with recipes.
Recent activity from embed and lime
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 6mo agoembedstep_umap() zero-component bug fixed
- 8mo agolimeCompatibility across all xgboost versions
- 8mo agoembedCompatibility with all xgboost versions
- 11mo agoembedstep_lencode() adds analytical likelihood encoding with pooling
- 1y agoembedUMAP initial and target_weight become tunable
- 2y agoembedkeras and tensorflow moved to Suggests
- 2y agoembedstep_collapse_stringdist() returns factors
- 3y agolimeMaintainer handover to Emil Hvitfeldt
- 5y agolimeorder() fix and lighter dependencies
- 6y agolimeNamespace fix following glmnet changes
- 7y agolimeexplain() gains pass-through args and gower_pow tuning
- 8y agolimeh2o support, NA handling and date feature types
Frequently asked questions
What is the difference between embed and lime?
They serve adjacent needs but don't currently overlap on shipped themes. embed and lime 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 embed better than lime?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. embed and lime 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 embed?
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.
What are the best alternatives to lime?
Top lime alternatives in Analytics are ranked by recent ship velocity. Browse the "lime alternatives" section above for the current picks, or visit /alternatives/lime-r for the full list with editorial commentary on each.