fillpattern
Pattern fills for ggplot2, hardened against the ways users write sizes
Comparison · Analytics
ggstats vs vim
A side-by-side editorial comparison of ggstats and vim — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
ggstats vs vim: at a glance
What is ggstats?
ggstats keeps widening what a coefficient or Likert plot can be
ggstats extends ggplot2 with statistical plotting: model coefficient plots, Likert and diverging bar charts, proportion geometries and the helpers that make them behave. Recent releases have added an experimental gglikert_side(), left and right total columns for gglikert(), and survey-object support across the Likert family. Development is steady and CRAN-paced, with releases every two to three months.
What is vim?
Six dormant years end with a correctness audit across VIM's entire imputation surface
VIM handles visualization and imputation of missing values in R, with kNN, hot-deck, iterative robust model-based imputation and matching-based methods. Development effectively stopped after 6.0.0 in 2020. Version 7.2.0 arrives in July 2026 as an explicitly framed correctness milestone: MI-properness warnings, ordered-factor preservation, a keep_all_columns option, list returns from irmi(mi>1), repairs to imputeRobust and imputeRobustChain, cellwise IRWLS and initial-weight fixes, and kNN and gowerD mixed-scaling corrections with a weightDist guard.
ggstats vs vim: editorial side-by-side
ggstats
0.0ANALYTICS
ggstats keeps widening what a coefficient or Likert plot can be
◆ Current state
ggstats extends ggplot2 with statistical plotting: model coefficient plots, Likert and diverging bar charts, proportion geometries and the helpers that make them behave. Recent releases have added an experimental gglikert_side(), left and right total columns for gglikert(), and survey-object support across the Likert family. Development is steady and CRAN-paced, with releases every two to three months.
◆ Where it's heading
Two long-running threads. The coefficient side has been consolidating — ggcoef_multinom() and ggcoef_multicomponents() soft-deprecated in favour of a unified ggcoef_model() with group_by, plus new ggcoef_dodged() and ggcoef_faceted() variants. The Likert side keeps expanding outward instead, absorbing survey objects, total columns and side-by-side layouts. Underneath both is a steady tax of ggplot2 and vctrs compatibility work, including tracking the geom_errorbarh() deprecation in ggplot2 4.0.0.
◆ Prediction
Expect gglikert_side() to lose its experimental status once its interface settles, and the deprecated multinomial entry points to be removed in a future release now that ggcoef_model() covers their cases.
vim
0.0ANALYTICS
Six dormant years end with a correctness audit across VIM's entire imputation surface
◆ Current state
VIM handles visualization and imputation of missing values in R, with kNN, hot-deck, iterative robust model-based imputation and matching-based methods. Development effectively stopped after 6.0.0 in 2020. Version 7.2.0 arrives in July 2026 as an explicitly framed correctness milestone: MI-properness warnings, ordered-factor preservation, a keep_all_columns option, list returns from irmi(mi>1), repairs to imputeRobust and imputeRobustChain, cellwise IRWLS and initial-weight fixes, and kNN and gowerD mixed-scaling corrections with a weightDist guard.
◆ Where it's heading
The release notes describe an audit — Wave 1 plus tail — rather than a feature cycle, and the fixes cluster around statistical validity: whether multiple imputation is proper, whether factor ordering survives, whether distance scaling across mixed variable types is right. Those are the properties users cannot easily verify themselves, so a package correcting them after six years is implicitly restating what its earlier output was worth. The notes also name a forthcoming R Journal paper under the name vimpute, which points at a successor or companion identity.
◆ Prediction
The entries call this a stable reference point for a paper and refer to Wave 1, so a further audit wave is the most likely next release; the vimpute naming is worth watching but the entries do not say what it is.
Alternatives to ggstats and vim
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 ggstats or vim.
gcube
gcube's recent releases are all packaging metadata, not simulation code
cubist
The R port of Quinlan's Cubist gets reproducibility fixes, not new modelling
ecodive
ecodive rebuilt itself into a broad diversity-metric library, breaking as it went
simStateSpace
State-space data simulation for R, filled in one function at a time
rollama
rollama turns a local-LLM wrapper into an instrument for reproducible annotation
Recent activity from ggstats and vim
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agovimCorrectness audit fixes MI-properness, factor order and distance scaling
- 5mo agoggstatsgglikert_side() and total columns for Likert plots
- 7mo agoggstatsLikert functions accept survey objects
- 11mo agoggstatsTable output for ggcoef_compare(); x-axis limits harmonised
- 1y agoggstatsggstats 0.10.0
- 1y agoggstatsCoefficient plots unified around ggcoef_model() with grouping
- 1y agoggstatsDiverging and Likert geoms redesigned; connector geoms added
- 6y agovimAdds ranger-based imputation, drops survey and GUI support
- 6y agovimAdds nine example datasets and splits help pages
- 6y agovimAdds matchImpute() and random-forest augmented kNN
- 6y agovimOrdered factor support and ordinal regression in irmi()
- 6y agovimBug fixes for kNN, hotdeck and irmi input handling
Frequently asked questions
What is the difference between ggstats and vim?
Both compete on the same themes — r-package — within Analytics. ggstats and vim 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 ggstats better than vim?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ggstats and vim 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 ggstats?
Top ggstats alternatives in Analytics are ranked by recent ship velocity. Browse the "ggstats alternatives" section above for the current picks, or visit /alternatives/ggstats for the full list with editorial commentary on each.
What are the best alternatives to vim?
Top vim alternatives in Analytics are ranked by recent ship velocity. Browse the "vim alternatives" section above for the current picks, or visit /alternatives/vim for the full list with editorial commentary on each.