← Back to home
Comparison · Analytics

ggtrace vs tbrf

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

Shared themes:r-package

ggtrace vs tbrf: at a glance

Featureggtracetbrf
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesggplot2, debugging, ggproto, developer-toolingrolling-statistics, water-quality, time-series, environmental-data
Last editorial update1h ago1h 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 tbrf?

Time-based rolling statistics for water-quality data, finally getting plotting and padding built in.

tbrf computes rolling statistics over time windows rather than fixed row counts — geometric means, confidence intervals and related summaries indexed by date. That distinction matters for irregularly sampled environmental monitoring data, where a fixed-width window spans different amounts of real time. Version 0.1.7 folds in stat_stepribbon() from ggalt, ships an Entero example dataset for lognormal workflows, and adds na.pad across the tbr_ family.

Read the full tbrf trajectory →

ggtrace vs tbrf: 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.

T
tbrf
ANALYTICS
0.0

Time-based rolling statistics for water-quality data, finally getting plotting and padding built in.

◆ Current state

tbrf computes rolling statistics over time windows rather than fixed row counts — geometric means, confidence intervals and related summaries indexed by date. That distinction matters for irregularly sampled environmental monitoring data, where a fixed-width window spans different amounts of real time. Version 0.1.7 folds in stat_stepribbon() from ggalt, ships an Entero example dataset for lognormal workflows, and adds na.pad across the tbr_ family.

◆ Where it's heading

The package spent its middle releases absorbing upstream breakage — a lubridate duration redefinition, a tibble 3.0.0 subassignment change, tidyselect internals. The 0.1.7 release breaks that pattern: it is the first in five years to add capability rather than repair it, and it does so by internalising a stat from an abandoned dependency instead of relying on it. Cadence remains very low, with a five-year gap between 0.1.5 and 0.1.6.

◆ Prediction

Absorbing stat_stepribbon() directly suggests further vendoring of the plotting layer rather than new statistical functions. The entries do not indicate which rolling statistics, if any, are queued next.

Alternatives to ggtrace and tbrf

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 tbrf.

See all ggtrace alternatives → · See all tbrf alternatives →

Recent activity from ggtrace and tbrf

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

  1. 0y agotbrfstat_stepribbon vendored in, plus na.pad on all rolling functions
  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 agotbrfgm_mean_ci forwards na.rm and zero.propagate correctly
  7. 1y agoggtracetrace_steps = "all" added; double-evaluation side effects fixed
  8. 1y agoggtracelayer_is() targets by_layer() downstream directly
  9. 6y agotbrfFix internals broken by tibble 3.0.0 subassignment
  10. 6y agotbrfDate windows recomputed with intervals and periods

Frequently asked questions

What is the difference between ggtrace and tbrf?

Both compete on the same themes — r-package — within Analytics. ggtrace and tbrf 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 tbrf?

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

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