rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of ggsketch and surveytidy — release velocity, themes, recent moves, and the top alternatives to consider.
ggsketch stopped being a line style and became a drawing-medium simulator.
ggsketch is a ggplot2 extension that renders plots as if drawn by hand. Through the 1.x line that meant one thing: roughening outlines and fills with configurable jitter. The 2.0.0 release published in July reframes the package around simulated drawing media — pen, chisel-tip highlighter, airbrush — and simulated paper grounds, with the sketch geoms inheriting whichever medium is set.
surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.
surveytidy is the tidyverse-facing half of a two-package survey stack, wrapping survey design objects from surveycore so filter, mutate, select and the rest work on them while carrying variable labels, value labels and a transformation log alongside the data. The May release extended that verb surface to survey_collection, the abstraction surveycore uses to hold several surveys as one object, so a pipeline written once dispatches across every member.
ggsketch is a ggplot2 extension that renders plots as if drawn by hand. Through the 1.x line that meant one thing: roughening outlines and fills with configurable jitter. The 2.0.0 release published in July reframes the package around simulated drawing media — pen, chisel-tip highlighter, airbrush — and simulated paper grounds, with the sketch geoms inheriting whichever medium is set.
The maintainer states 2.0.0 is the engine for a series, and the release notes read that way: the medium sampler and the paper renderer are new Layer-1/Layer-2 primitives that every existing geom picks up for free. The second thread is correctness under real plot layouts — corner-aware label repulsion, boundary densification so bars bend under polar coordinates, reserved panel room so edge labels stop clipping. Geom coverage keeps widening in parallel, with chicklet charts the newest addition.
Expect the rest of the 2.x series to add media on top of the new sampler rather than more geoms, since that is where 2.0.0 put the extensibility. The default hachure-pitch change already shifts existing output slightly, so a follow-up patch tuning those defaults against real plots is likely.
surveytidy is the tidyverse-facing half of a two-package survey stack, wrapping survey design objects from surveycore so filter, mutate, select and the rest work on them while carrying variable labels, value labels and a transformation log alongside the data. The May release extended that verb surface to survey_collection, the abstraction surveycore uses to hold several surveys as one object, so a pipeline written once dispatches across every member.
The package is being built in two layers that arrive in order: vector-level transformations first, structural dispatch second. The make_* family in 0.4.0 handles the recoding that survey work actually consists of — labelled to factor, multi-level to dichotomous, scale reversal, valence flipping — with value labels propagating automatically. Collection support then applies data-masking, tidyselect, grouping, slicing and collapsing verbs per survey, with joins explicitly refused and a typed message reporting which surveys were skipped. Metadata fidelity is the recurring bug source: labels surviving across(), stale labels left behind by recoding, the transformation log keeping up with what the verbs did.
Joins are the one verb family that errors on collections, with users directed to join before constructing the collection, so that restriction is the clearest outstanding gap. The re-export of surveycore's collection constructors suggests the package is positioning itself as the single import users need, which points toward more re-exports as surveycore's stable API settles.
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 ggsketch or surveytidy.
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 ggsketch alternatives → · See all surveytidy alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. ggsketch and surveytidy 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ggsketch and surveytidy 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 Infra & APIs products to evaluate alongside.
Top ggsketch alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ggsketch alternatives" section above for the current picks, or visit /alternatives/ggsketch for the full list with editorial commentary on each.
Top surveytidy alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "surveytidy alternatives" section above for the current picks, or visit /alternatives/surveytidy for the full list with editorial commentary on each.