simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of ggtrace and reda — release velocity, themes, recent moves, and the top alternatives to consider.
A debugger for ggplot2's internals, hardening its grip as the internals it traces keep moving.
ggtrace lets users step inside ggplot2's rendering pipeline — tracing ggproto methods, dumping intermediate state, and snapshotting layer data at each stage via layer_before_stat(), layer_after_stat(), layer_before_geom() and layer_after_scale(). The workflow functions gained short aliases at 0.7.1, and recent releases have gone into making method resolution work on ggproto definitions written in forms the tracer did not originally expect.
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.
ggtrace lets users step inside ggplot2's rendering pipeline — tracing ggproto methods, dumping intermediate state, and snapshotting layer data at each stage via layer_before_stat(), layer_after_stat(), layer_before_geom() and layer_after_scale(). The workflow functions gained short aliases at 0.7.1, and recent releases have gone into making method resolution work on ggproto definitions written in forms the tracer did not originally expect.
The package matured from raw tracing primitives into named workflows: 0.6.0 added the sublayer snapshot functions and error-context helpers, 0.7.x has been sanding down how reliably those workflows find and evaluate a method. Three consecutive releases in May 2025, two of them minutes apart, all address the same class of failure — one-liner ggproto methods without braces, and inheritance resolution on instances rather than subclasses. That pattern says the remaining bugs are in method introspection, not in the tracing machinery itself.
Expect continued fixes to method resolution as ggplot2's ggproto definitions vary, and realignment work when ggplot2 4.x changes internals this package deliberately reaches into. The entries do not signal new workflow functions.
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.
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.
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.
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 ggtrace or reda.
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
A raster-to-terra migration is the only readable change in a feed of merge notes.
A nycflights13 generator whose recent work is all about the data being right.
Conditional density and log-likelihood fill out a vine copula regression package.
A drop-in string API for base R, kept alive by upstream check failures.
See all ggtrace alternatives → · See all reda alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. ggtrace and reda 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ggtrace and reda 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.
Top ggtrace alternatives in Analytics are ranked by recent ship velocity. Browse the "ggtrace alternatives" section above for the current picks, or visit /alternatives/ggtrace for the full list with editorial commentary on each.
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.