simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
Comparison · Analytics
ggtrace vs lstar
A side-by-side editorial comparison of ggtrace and lstar — release velocity, themes, recent moves, and the top alternatives to consider.
ggtrace vs lstar: at a glance
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.
What is lstar?
A single-cell data store commits to Zarr v3 and range-readable hosting across four language surfaces
lstar stores single-cell data behind one C++ core with Python, R and JS/WASM bindings, and ships a browser viewer that reads the store directly. Zarr v3 is now the default on-disk format across all four surfaces, with zstd compression and sharding that packs many chunks into fewer objects. Viewer stores are compressed per field and resolved at chunk granularity, so a hosted viewer fetches only what it displays. The tag stream carries both lstar and lstar-sc releases.
ggtrace vs lstar: editorial side-by-side
ggtrace
0.0ANALYTICS
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.
lstar
5.0ANALYTICS
A single-cell data store commits to Zarr v3 and range-readable hosting across four language surfaces
◆ Current state
lstar stores single-cell data behind one C++ core with Python, R and JS/WASM bindings, and ships a browser viewer that reads the store directly. Zarr v3 is now the default on-disk format across all four surfaces, with zstd compression and sharding that packs many chunks into fewer objects. Viewer stores are compressed per field and resolved at chunk granularity, so a hosted viewer fetches only what it displays. The tag stream carries both lstar and lstar-sc releases.
◆ Where it's heading
The through-line is making a hosted store cheap to read. Sharding addresses the file-per-chunk explosion that makes many-chunk arrays awkward to host; per-field compression with chunk-granular resolution means colouring an embedding by one gene fetches one column rather than an array. The 0.2.x patches are the cost of maintaining four surfaces at once — a WASM heap crash that only browsers exercise, and a count-basis orientation defect where all three surfaces normalized in memory and none owned the on-disk layout.
◆ Prediction
The orientation bug's root cause — no surface owning the on-disk representation while all three normalized in memory — is the kind of gap that usually produces a validation or ownership change rather than another point fix.
Alternatives to ggtrace and lstar
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 lstar.
lavaanExtra
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
ibis.iSDM
A raster-to-terra migration is the only readable change in a feed of merge notes.
anyflights
A nycflights13 generator whose recent work is all about the data being right.
vinereg
Conditional density and log-likelihood fill out a vine copula regression package.
stringx
A drop-in string API for base R, kept alive by upstream check failures.
See all ggtrace alternatives → · See all lstar alternatives →
Recent activity from ggtrace and lstar
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 21d agolstarViewer count-basis orientation fixed; existing stores need re-prep
- 26d agolstarWASM viewer crash on resizable heaps fixed
- 1mo agolstarlstar 0.2.0 ⚡
- 1mo agolstarMeasure state inferred from content, not slot name
- 1y agoggtraceBrace-less one-liner methods traced gracefully
- 1y agoggtraceget_method_inheritance() fixed for class instances
- 1y agoggtraceWorkflow functions recognise one-liner ggproto methods
- 1y agoggtraceEager layer_is(), clearer method-mismatch errors, consistent tracedump names
- 1y agoggtracetrace_steps = "all" added; double-evaluation side effects fixed
- 1y agoggtracelayer_is() targets by_layer() downstream directly
Frequently asked questions
What is the difference between ggtrace and lstar?
They serve adjacent needs but don't currently overlap on shipped themes. lstar is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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.
Is ggtrace better than lstar?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. lstar is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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.
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 lstar?
Top lstar alternatives in Analytics are ranked by recent ship velocity. Browse the "lstar alternatives" section above for the current picks, or visit /alternatives/lstar for the full list with editorial commentary on each.