simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of ggtrace and glydraw — 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.
SNFG glycan cartoons stopped being pictures and became ggplot2 geoms, guides and axis labels.
glydraw renders glycan structures as SNFG-standard cartoons, standalone or exported in bulk, and since 0.7.0 as native ggplot2 components: geom_glycan() for observations, geom_node_glycan() for ggraph networks, guide_glycan() for legends, and scale_x_glycan() and scale_y_glycan() for discrete axes. Appearance is configured through a single reusable style object rather than scattered arguments, a consolidation that 0.8.0 made breaking. The colour handling now expects a complete SNFG palette rather than sparse per-monosaccharide overrides.
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.
glydraw renders glycan structures as SNFG-standard cartoons, standalone or exported in bulk, and since 0.7.0 as native ggplot2 components: geom_glycan() for observations, geom_node_glycan() for ggraph networks, guide_glycan() for legends, and scale_x_glycan() and scale_y_glycan() for discrete axes. Appearance is configured through a single reusable style object rather than scattered arguments, a consolidation that 0.8.0 made breaking. The colour handling now expects a complete SNFG palette rather than sparse per-monosaccharide overrides.
The first half of this record is geometry correctness, fixing branch spacing, overlapping linkage annotations, core fucose collisions, triangle alignment and nested side-chain layout, because a cartoon that draws the wrong topology is worse than no cartoon. Once the drawing was trustworthy the package moved outward into ggplot2 and then inward again to consolidate its own API, dropping the glyexp dependency, removing positional argument support, and folding rendering options into style_glydraw(). Each of the last several releases has been explicitly breaking, which is a maintainer using a pre-1.0 window deliberately.
With the style object established and the ggplot2 surface in place, the remaining explicit arguments, show_linkage and orient, are the visible inconsistency and may follow the others into the style. Sibling packages adopt each change within days, as glyenzy did with the new orientation values, so expect the next breaking change to propagate the same way.
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 glydraw.
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 glydraw alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — ggplot2 — within Analytics. glydraw is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. 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. glydraw is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. 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 glydraw alternatives in Analytics are ranked by recent ship velocity. Browse the "glydraw alternatives" section above for the current picks, or visit /alternatives/glydraw for the full list with editorial commentary on each.