tidytext
Finished, widely taught, and shipping roxygen fixes.
Comparison · Analytics
lime vs patchwork
A side-by-side editorial comparison of lime and patchwork — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:maintenance
lime vs patchwork: at a glance
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.
What is patchwork?
patchwork stopped being a ggplot composer and became a page composer.
patchwork assembles plots into compositions with arithmetic operators, and the 1.x line has steadily hardened that grammar: guide and axis collection, free() to exempt a plot from alignment, inset_element() for overlays, and list-like behaviour so lapply() and length() work on a patchwork. Version 1.3.0 added native gt table support. The two releases since are a load-time warning fix and a compatibility pass for the next ggplot2 release.
lime vs patchwork: editorial side-by-side
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.
patchwork
0.0ANALYTICS
patchwork stopped being a ggplot composer and became a page composer.
◆ Current state
patchwork assembles plots into compositions with arithmetic operators, and the 1.x line has steadily hardened that grammar: guide and axis collection, free() to exempt a plot from alignment, inset_element() for overlays, and list-like behaviour so lapply() and length() work on a patchwork. Version 1.3.0 added native gt table support. The two releases since are a load-time warning fix and a compatibility pass for the next ggplot2 release.
◆ Where it's heading
The centre of gravity is shifting from alignment mechanics to composition scope. Early releases were almost entirely bug fixes against grid and ggplot2 internals — strip placement, fixed aspect ratios, guide merging. Recent ones add object types and escape hatches instead. Between feature cycles the package is in maintenance defined by ggplot2's release calendar, which is what 1.3.1 is in its entirety.
◆ Prediction
Expect wrap_table() to grow beyond gt to other table objects, and expect the next substantive release to be triggered by a ggplot2 internals change rather than by a patchwork roadmap.
Alternatives to lime and patchwork
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 lime or patchwork.
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 lime alternatives → · See all patchwork alternatives →
Recent activity from lime and patchwork
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 8mo agolimeCompatibility across all xgboost versions
- 11mo agopatchworkFix spurious load-time warnings
- 1y agopatchworkCompatibility pass for the next ggplot2 release
- 1y agopatchworkgt tables become first-class patchwork objects ⚡
- 2y agopatchworkAxis collection and free() arrive
- 3y agopatchworkPatchworks behave like lists; NULL becomes a no-op
- 3y agopatchworkClearer error when plotting space is too small
- 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 lime and patchwork?
Both compete on the same themes — maintenance — within Analytics. lime and patchwork 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 lime better than patchwork?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. lime and patchwork 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 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.
What are the best alternatives to patchwork?
Top patchwork alternatives in Analytics are ranked by recent ship velocity. Browse the "patchwork alternatives" section above for the current picks, or visit /alternatives/patchwork for the full list with editorial commentary on each.