rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
Comparison · Infra & APIs
robscale vs surveycore
A side-by-side editorial comparison of robscale and surveycore — release velocity, themes, recent moves, and the top alternatives to consider.
robscale vs surveycore: at a glance
What is robscale?
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.
What is surveycore?
surveycore declared its API stable with every survey design type covered.
surveycore is the estimation engine of a two-package survey stack, handling design objects and variance estimation while surveytidy supplies the dplyr verbs on top. The June release marks it 1.0.0 and states the API is complete and stable across Taylor series linearization, replicate weights, two-phase and non-probability designs, with means, totals, frequencies, quantiles, ratios, correlations, regression, t-tests, ANOVA and effective sample size all in place.
robscale vs surveycore: editorial side-by-side
robscale
0.0INFRA · APIS
A robust-statistics package rewrote its estimators in SIMD C++ and went to CRAN in two weeks.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
surveycore
0.0INFRA · APIS
surveycore declared its API stable with every survey design type covered.
◆ Current state
surveycore is the estimation engine of a two-package survey stack, handling design objects and variance estimation while surveytidy supplies the dplyr verbs on top. The June release marks it 1.0.0 and states the API is complete and stable across Taylor series linearization, replicate weights, two-phase and non-probability designs, with means, totals, frequencies, quantiles, ratios, correlations, regression, t-tests, ANOVA and effective sample size all in place.
◆ Where it's heading
The last months before 1.0.0 were spent making the awkward designs behave like the ordinary ones. Non-probability designs gained jackknife replicate schemes and got their bootstrap repweights routed through the replicate-weight variance estimator in survey_glm(), matching every other estimation function. The survey_collection abstraction — several surveys treated as one pseudo-data-frame — was tightened rather than extended: divergent grouping across members now errors instead of stitching a patchwork with bind_rows(), and the missing-variable argument was renamed and given a stored default on the collection itself. A documentation audit before 1.0.0 turned up six dispatch and print bugs and corrections across forty-plus files, which is the kind of thing that surfaces when an API is being frozen rather than extended.
◆ Prediction
A declared-stable API means the next releases should be additive or corrective rather than breaking, and the pre-1.0.0 pattern of breaking renames should stop. The tight version pinning between the two packages means surveytidy releases will keep following surveycore's.
Alternatives to robscale and surveycore
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 surveycore.
massProps
A mass-properties rollup spends a year on documentation and follows its sibling's API
writeAlizer
Six months of releases and not one of them touched the scoring models
samplr
A cognitive-science sampling package ships once, then goes quiet for eighteen months
stochvol
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
midr
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
See all robscale alternatives → · See all surveycore alternatives →
Recent activity from robscale and surveycore
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agosurveycoreFirst stable release: all four survey design types complete ⚡
- 3mo agosurveycoreget_effective_n() computes effective sample size
- 3mo agosurveycoreCollections error on divergent grouping; .on_missing renamed
- 4mo agosurveycoreCRAN patch removing surveytidy from the vignette
- 4mo agorobscaleSIMD median networks land; AVX-512 dispatch is dropped
- 4mo agorobscaleCRAN submission ships 11 robust estimators with bootstrap intervals ⚡
- 5mo agorobscalescale_robust() dispatcher and four new estimators join the public API
Frequently asked questions
What is the difference between robscale and surveycore?
They serve adjacent needs but don't currently overlap on shipped themes. robscale and surveycore 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 robscale better than surveycore?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. robscale and surveycore 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.
What are the best alternatives to robscale?
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.
What are the best alternatives to surveycore?
Top surveycore alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "surveycore alternatives" section above for the current picks, or visit /alternatives/surveycore for the full list with editorial commentary on each.