tidytext
Finished, widely taught, and shipping roxygen fixes.
Comparison · Analytics
datawizard vs lime
A side-by-side editorial comparison of datawizard and lime — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-stats
datawizard vs lime: at a glance
What is datawizard?
datawizard is turning easystats' data layer into a general-purpose I/O and reshaping tool
datawizard handles the data preparation half of the easystats stack — reshaping, recoding, describing, and reading and writing files. The 1.x releases have pushed hardest on I/O: parquet via nanoparquet, then password-protected R formats, alongside a run of breaking cleanups in data_to_wide(), data_modify() and describe_distribution().
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.
datawizard vs lime: editorial side-by-side
datawizard
0.0ANALYTICS
datawizard is turning easystats' data layer into a general-purpose I/O and reshaping tool
◆ Current state
datawizard handles the data preparation half of the easystats stack — reshaping, recoding, describing, and reading and writing files. The 1.x releases have pushed hardest on I/O: parquet via nanoparquet, then password-protected R formats, alongside a run of breaking cleanups in data_to_wide(), data_modify() and describe_distribution().
◆ Where it's heading
The package is willing to break its own interfaces to reach behavior users expect from tidyr and friends — data_to_wide() explicitly moved toward pivot_wider() semantics, and data_modify() stopped guessing whether a string was an expression. Output formatting is consolidating behind insight's display() and tinytable. The direction is fewer surprises and more file formats, not more statistics.
◆ Prediction
Expect encryption and format support to extend past R-native files if it continues, and further alignment of print and display behavior with the shared insight infrastructure.
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 datawizard 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 datawizard 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 datawizard alternatives → · See all lime alternatives →
Recent activity from datawizard and lime
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agodatawizardEncrypted data files via a password argument on read/write
- 8mo agolimeCompatibility across all xgboost versions
- 10mo agodatawizarddata_to_wide() moves toward pivot_wider() semantics
- 1y agodatawizardParquet read and write support via nanoparquet
- 1y agodatawizarddata_modify() stops inferring expressions from strings
- 1y agodatawizarddatawizard 1.0.2
- 1y agodatawizarddata_arrange() preserves single-column data frames
- 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 datawizard and lime?
Both compete on the same themes — r-stats — within Analytics. datawizard 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 datawizard better than lime?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. datawizard 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 datawizard?
Top datawizard alternatives in Analytics are ranked by recent ship velocity. Browse the "datawizard alternatives" section above for the current picks, or visit /alternatives/datawizard 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.