rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of robscale and surveytidy — release velocity, themes, recent moves, and the top alternatives to consider.
A robust-statistics package rewrote its estimators in SIMD C++ and went to CRAN in two weeks.
robscale computes robust scale and location estimators, and its pitch is speed: 21 to 26 times faster than stats::mad, 37 times faster than stats::IQR on small samples, with comparable margins over robustbase for Qn and Sn. The March 2026 releases took it from a GitHub project to a CRAN package carrying eleven estimators, all with confidence intervals.
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.
robscale computes robust scale and location estimators, and its pitch is speed: 21 to 26 times faster than stats::mad, 37 times faster than stats::IQR on small samples, with comparable margins over robustbase for Qn and Sn. The March 2026 releases took it from a GitHub project to a CRAN package carrying eleven estimators, all with confidence intervals.
Three releases in a fortnight walk a clear line: expand the public API, submit to CRAN, then tune. The 0.5.4 work is where that tuning shows, and it is unusually specific about hardware, raising sorting-network thresholds after benchmarking and dropping the AVX-512 path entirely in favour of a shorter AVX2-first dispatch chain. The build-fix lists are long, which is what a package fighting compiler and TBB variation across CRAN's platforms looks like.
The dispatch hierarchy has been simplified once already; further releases most likely continue narrowing the SIMD surface and hardening the configure step rather than adding estimators. A new estimator would be the surprise.
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 robscale 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 robscale 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. robscale 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. robscale 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 robscale alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "robscale alternatives" section above for the current picks, or visit /alternatives/robscale 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.