rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of ggpointless and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.
ggpointless keeps adding the ggplot2 layers nobody else bothered to write.
ggpointless is a small ggplot2 extension collecting geoms that sit outside the standard set — Lexis diagrams, Chaikin-smoothed paths, hanging chains, Fourier reconstructions — and it has grown steadily rather than changed shape. The May release is the largest yet: isotype and pictogram bar charts as stacks of discrete unit cells, a family of geoms that fade paths, segments, curves and reference lines along their length, and geom_gridline(), which draws grid lines as a layer on top of the data rather than beneath it.
Skipper trims a 4x memory regression out of routesrv, days after shipping h2c
Zalando's HTTP router ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.63, which stops routesrv holding an uncompressed route tree alongside the compressed buffer: retained memory in the release's own benchmark falls from 30.7 MB to 2.0 MB, undoing most of the 4x increase zone-aware routing had introduced. Around it sit narrow auth repairs, and an eskip parser change that finally accepts negative numeric arguments in predicates and filters.
ggpointless is a small ggplot2 extension collecting geoms that sit outside the standard set — Lexis diagrams, Chaikin-smoothed paths, hanging chains, Fourier reconstructions — and it has grown steadily rather than changed shape. The May release is the largest yet: isotype and pictogram bar charts as stacks of discrete unit cells, a family of geoms that fade paths, segments, curves and reference lines along their length, and geom_gridline(), which draws grid lines as a layer on top of the data rather than beneath it.
Two patterns are visible. Ideas get generalized rather than left as one-offs: geom_area_fade() in the previous release established alpha gradients via grid::linearGradient(), and the recent release spreads that treatment across paths, lines, steps, segments, curves and the three reference-line geoms, each with the same fade_direction and alpha_fade_to arguments. And each new geom is expected to survive real plots — the unit charts work under coord_equal, coord_polar, coord_radial, coord_flip and faceting, and geom_gridline reads positions from trained scales and inherits styling from the theme's panel grid. The package also tracks ggplot2 closely, requiring 4.0.0 and using make_constructor() and gg_par() internally, and it dropped its bundled datasets outright rather than maintain stale copies.
The fade treatment now covers most path-like geoms but not the area and ribbon family beyond geom_area_fade(), which is where the pattern has room left to run. The unit-cell charts arrive with a label helper and no fill or grouping variants, so those are the plausible next additions.
Zalando's HTTP router ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.63, which stops routesrv holding an uncompressed route tree alongside the compressed buffer: retained memory in the release's own benchmark falls from 30.7 MB to 2.0 MB, undoing most of the 4x increase zone-aware routing had introduced. Around it sit narrow auth repairs, and an eskip parser change that finally accepts negative numeric arguments in predicates and filters.
Two threads run through the recent tags. The data path keeps getting real work - leastRequests balancing, then h2c end to end in v0.27.57, now the memory cost of zone-aware routing being paid back. The auth filters, by contrast, are only being maintained: token introspection, grant auth, and now the OIDC Referer handling are fixes rather than new capability, and several are follow-ups to each other rather than independent bugs.
Zone-aware routing looks like the source of the recent memory attention, so expect further tuning around route storage and the hash computation done on every pull, which the release's second benchmark already isolates. The OIDC cookie change is the second link in an auth chain that started with the grant-auth fix, and is likely to draw another follow-up.
Other Infra & APIs 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 ggpointless or Skipper.
The recursive-computation engine under massProps grows the accessors its consumer needed
A mass-properties rollup spends a year on documentation and follows its sibling's API
Six months of releases and not one of them touched the scoring models
A cognitive-science sampling package ships once, then goes quiet for eighteen months
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
See all ggpointless alternatives → · See all Skipper alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Skipper 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Skipper 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 Infra & APIs products to evaluate alongside.
Top ggpointless alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ggpointless alternatives" section above for the current picks, or visit /alternatives/ggpointless for the full list with editorial commentary on each.
Top Skipper alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Skipper alternatives" section above for the current picks, or visit /alternatives/skipper for the full list with editorial commentary on each.