STACAS
Single-cell batch correction that learned to use cell labels, then spent three releases chasing Seurat.
Comparison · Analytics
reda vs vim
A side-by-side editorial comparison of reda and vim — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
reda vs vim: at a glance
What is reda?
A mature recurrent-event toolkit in careful maintenance, shedding weight rather than adding surface.
reda provides nonparametric mean cumulative function estimation, gamma-frailty rate regression, and event-data simulation for recurrent-event survival analysis. The core API settled at 0.5.0 when Recur() replaced Survr() and the MCF internals moved to C++. Everything since has been consolidation: small argument additions, method completions, and CRAN hygiene.
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.
reda vs vim: editorial side-by-side
reda
0.0ANALYTICS
A mature recurrent-event toolkit in careful maintenance, shedding weight rather than adding surface.
◆ Current state
reda provides nonparametric mean cumulative function estimation, gamma-frailty rate regression, and event-data simulation for recurrent-event survival analysis. The core API settled at 0.5.0 when Recur() replaced Survr() and the MCF internals moved to C++. Everything since has been consolidation: small argument additions, method completions, and CRAN hygiene.
◆ Where it's heading
The last three releases contain no new modelling capability at all — a dependency reshuffle, a test-example correction, and a print-order fix. The package is being kept installable and correct rather than extended. Its tightest coupling is to splines2, a sibling package from the same maintainer, which supplies the derivative machinery reda depends on.
◆ Prediction
Expect continued small-cadence CRAN-compliance releases tracking ggplot2 and splines2 changes. The entries show no in-progress feature work, so a substantive release would have to arrive without warning from this feed.
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 reda 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 reda or vim.
ggtrace
A debugger for ggplot2's internals, hardening its grip as the internals it traces keep moving.
kde1d
A univariate density estimator that added zero-inflated data and reopened its C++ API to do it.
svines
Stationary vine copulas for time series, released in lockstep with the rest of Nagler's vine stack.
gghighlight
A single-purpose ggplot2 extension that has spent six years tracking ggplot2 instead of growing.
rtrek
A Star Trek data package that became a Memory Alpha web client and has been patching scrapers ever since.
Recent activity from reda and vim
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agovimCorrectness audit fixes MI-properness, factor order and distance scaling
- 11mo agoredaggplot2 and grDevices demoted to Suggests
- 1y agoredaTest example and documentation typo fixes
- 4y agoredasimEvent() gains a user-supplied rate bound
- 5y agoredasummary() method completes the Recur object
- 5y agoredaDerivatives sourced from splines2's deriv method
- 6y agovimAdds ranger-based imputation, drops survey and GUI support
- 6y agoredaMCF estimates can now skip variance computation
- 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 reda and vim?
Both compete on the same themes — r-package — within Analytics. reda 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 reda better than vim?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. reda 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 reda?
Top reda alternatives in Analytics are ranked by recent ship velocity. Browse the "reda alternatives" section above for the current picks, or visit /alternatives/reda 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.