← Back to home
Comparison · Analytics

crossmap vs ggtrace

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

crossmap vs ggtrace: at a glance

Featurecrossmapggtrace
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themespurrr extension, functional programming, deprecations, furrrggplot2, debugging, ggproto, developer-tooling
Last editorial update2h ago46m ago
WebsiteVisit →Visit →

What is crossmap?

crossmap's roadmap is set by purrr and furrr — it deprecates what upstream deprecates.

A small package for mapping over combinations of arguments, following purrr and furrr conventions. Its own functional additions stopped after xpluck() in 2023 and the cross_fit() clustering work in 2022. Everything since tracks upstream: xmap_raw() and future_xmap_raw() are now defunct because purrr removed map_raw() and furrr removed future_pmap_raw(), and re-exported parallel helpers now come from parallelly rather than future.

Read the full crossmap trajectory →

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 →

crossmap vs ggtrace: editorial side-by-side

C
crossmap
ANALYTICS
0.0

crossmap's roadmap is set by purrr and furrr — it deprecates what upstream deprecates.

◆ Current state

A small package for mapping over combinations of arguments, following purrr and furrr conventions. Its own functional additions stopped after xpluck() in 2023 and the cross_fit() clustering work in 2022. Everything since tracks upstream: xmap_raw() and future_xmap_raw() are now defunct because purrr removed map_raw() and furrr removed future_pmap_raw(), and re-exported parallel helpers now come from parallelly rather than future.

◆ Where it's heading

The package has settled into being a compatible extension rather than an independent one — its release notes read as a mirror of purrr's and furrr's deprecation schedules. Note that the release stamps are unreliable here: several versions were backfilled minutes apart and the 0.3.x tags carry timestamps in reverse version order, so feed position says nothing about what shipped when.

◆ Prediction

Expect the next release to be driven by another purrr or furrr change rather than new functionality, since that has been the sole trigger for the last four.

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.

Alternatives to crossmap and ggtrace

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 crossmap or ggtrace.

See all crossmap alternatives → · See all ggtrace alternatives →

Recent activity from crossmap and ggtrace

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

  1. 6mo agocrossmapRaw-vector mapping functions removed
  2. 6mo agocrossmapRe-exports moved to the parallelly namespace
  3. 11mo agocrossmapFuture-backed tests skipped on CRAN
  4. 11mo agocrossmapInternal test fixes
  5. 1y agoggtraceBrace-less one-liner methods traced gracefully
  6. 1y agoggtraceget_method_inheritance() fixed for class instances
  7. 1y agoggtraceWorkflow functions recognise one-liner ggproto methods
  8. 1y agoggtraceEager layer_is(), clearer method-mismatch errors, consistent tracedump names
  9. 1y agoggtracetrace_steps = "all" added; double-evaluation side effects fixed
  10. 1y agoggtracelayer_is() targets by_layer() downstream directly
  11. 3y agocrossmapxpluck adds multi-index plucking
  12. 4y agocrossmapCluster specifications supported in cross_fit

Frequently asked questions

What is the difference between crossmap and ggtrace?

They serve adjacent needs but don't currently overlap on shipped themes. crossmap and ggtrace 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 crossmap better than ggtrace?

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

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

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.