← Back to home
Comparison · Analytics

ggtrace vs healthyR.ts

A side-by-side editorial comparison of ggtrace and healthyR.ts — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:ggplot2

ggtrace vs healthyR.ts: at a glance

FeatureggtracehealthyR.ts
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesggplot2, debugging, ggproto, developer-toolingtime series, healthyverse, stationarity, ggplot2
Last editorial update55m ago3h ago
WebsiteVisit →Visit →

What is ggtrace?

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.

Read the full ggtrace trajectory →

What is healthyR.ts?

healthyR.ts keeps adding time-series helpers, then quietly breaks the old ones to modernise them.

A time-series companion in the healthyverse family, shipping helper functions in batches: growth-rate vectors, an ADF test and auto_stationarize() in 0.2.11, then five log and differencing transforms in 0.3.0, and a random-walk plot in 0.3.2. Alongside the additions runs a steady stream of breaking cleanups — invisible returns dropped, R 4.1 required for the native pipe, and ts_ma_plot() refactored onto ggplot2 facets with its xts output removed and its return value cut from six items to two.

Read the full healthyR.ts trajectory →

ggtrace vs healthyR.ts: editorial side-by-side

G
ggtrace
ANALYTICS
0.0

A debugger for ggplot2's internals, hardening its grip as the internals it traces keep moving.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

H
healthyR.ts
ANALYTICS
0.0

healthyR.ts keeps adding time-series helpers, then quietly breaks the old ones to modernise them.

◆ Current state

A time-series companion in the healthyverse family, shipping helper functions in batches: growth-rate vectors, an ADF test and auto_stationarize() in 0.2.11, then five log and differencing transforms in 0.3.0, and a random-walk plot in 0.3.2. Alongside the additions runs a steady stream of breaking cleanups — invisible returns dropped, R 4.1 required for the native pipe, and ts_ma_plot() refactored onto ggplot2 facets with its xts output removed and its return value cut from six items to two.

◆ Where it's heading

Two threads, both consistent. The functional one is coverage of the stationarity workflow — transform, test, auto-stationarize, plot — assembled function by function rather than as a single API. The structural one is convergence on ggplot2 and tidy conventions, retiring xts objects and multi-object return lists as it goes. The package is not afraid to break return shapes to get there, so upgrades are not drop-in.

◆ Prediction

Expect the remaining functions that still return xts objects or bundled lists to get the same ggplot2-only treatment, since ts_ma_plot() was refactored on exactly that rationale.

Alternatives to ggtrace and healthyR.ts

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 healthyR.ts.

See all ggtrace alternatives → · See all healthyR.ts alternatives →

Recent activity from ggtrace and healthyR.ts

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 6mo agohealthyR.tsRandom walk plot added; ts_ma_plot drops xts for ggplot2 facets
  2. 1y agoggtraceBrace-less one-liner methods traced gracefully
  3. 1y agoggtraceget_method_inheritance() fixed for class instances
  4. 1y agoggtraceWorkflow functions recognise one-liner ggproto methods
  5. 1y agoggtraceEager layer_is(), clearer method-mismatch errors, consistent tracedump names
  6. 1y agoggtracetrace_steps = "all" added; double-evaluation side effects fixed
  7. 1y agohealthyR.tsInvisible returns dropped; random walk and vva plot fixes
  8. 1y agoggtracelayer_is() targets by_layer() downstream directly
  9. 2y agohealthyR.tsFive log and differencing transform utilities added
  10. 2y agohealthyR.tsStationarity testing and auto_stationarize added
  11. 2y agohealthyR.tsSingle example fix
  12. 3y agohealthyR.tsBoilerplate fitting uses show_best directly

Frequently asked questions

What is the difference between ggtrace and healthyR.ts?

Both compete on the same themes — ggplot2 — within Analytics. ggtrace and healthyR.ts 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 ggtrace better than healthyR.ts?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ggtrace and healthyR.ts 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 ggtrace?

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.

What are the best alternatives to healthyR.ts?

Top healthyR.ts alternatives in Analytics are ranked by recent ship velocity. Browse the "healthyR.ts alternatives" section above for the current picks, or visit /alternatives/healthyr-ts for the full list with editorial commentary on each.