tidytext
Finished, widely taught, and shipping roxygen fixes.
Comparison · Analytics
discrim vs lime
A side-by-side editorial comparison of discrim and lime — release velocity, themes, recent moves, and the top alternatives to consider.
discrim vs lime: at a glance
What is discrim?
discrim settled into a thin engine shim after handing its model definitions to parsnip.
discrim is the parsnip extension for discriminant analysis, exposing linear, quadratic, flexible and regularized variants through the tidymodels interface. Its model definition functions moved into parsnip itself in 0.2.0, leaving this package as the engine and prediction layer. The two most recent releases are a documentation fix and a single prediction bug.
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.
discrim vs lime: editorial side-by-side
discrim
0.0ANALYTICS
discrim settled into a thin engine shim after handing its model definitions to parsnip.
◆ Current state
discrim is the parsnip extension for discriminant analysis, exposing linear, quadratic, flexible and regularized variants through the tidymodels interface. Its model definition functions moved into parsnip itself in 0.2.0, leaving this package as the engine and prediction layer. The two most recent releases are a documentation fix and a single prediction bug.
◆ Where it's heading
The package built out method coverage early, adding quadratic discriminant analysis in 0.1.2, the sda and sparsediscrim engines in 0.1.3 and case weights in 1.0.0, then stopped growing. Handing definitions upstream to parsnip in 0.2.0 confirmed the shape: discrim is where engines are wired, not where the API lives. Cadence since 2022 is roughly one small fix a year.
◆ Prediction
Nothing in the entries points to new methods or engines; the next release is most likely another CRAN or prediction-path fix.
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 discrim 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 discrim 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.
See all discrim alternatives → · See all lime alternatives →
Recent activity from discrim and lime
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 8mo agolimeCompatibility across all xgboost versions
- 8mo agodiscrimFix for FDA models failing at prediction time
- 11mo agodiscrimDocumentation links updated to stay on CRAN
- 3y agolimeMaintainer handover to Emil Hvitfeldt
- 4y agodiscrimCase weights enabled for flexible and linear discriminant models
- 4y agodiscrimModel definitions moved upstream into parsnip
- 5y agodiscrimsda and sparsediscrim engines added for LDA and QDA
- 5y agodiscrimdiscrim_quad() added; package relicensed to MIT ⚡
- 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 discrim and lime?
They serve adjacent needs but don't currently overlap on shipped themes. discrim 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 discrim better than lime?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. discrim 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 discrim?
Top discrim alternatives in Analytics are ranked by recent ship velocity. Browse the "discrim alternatives" section above for the current picks, or visit /alternatives/discrim 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.