rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of aftables and surveycore — release velocity, themes, recent moves, and the top alternatives to consider.
Accessible government spreadsheets in R, rebuilt on openxlsx2 and renamed along the way.
aftables generates spreadsheets that meet the UK Analysis Function's accessibility guidance, taking structured input and producing a formatted workbook with cover, contents, notes and table sheets. Version 2.0.0 replaced the workbook engine with openxlsx2 and added configuration through a config.yaml file, with create_config_yaml() exporting a template and generate_workbook() gaining arguments to point at it. The package was previously called a11ytables and was renamed in 1.0.2, with function names changed to match.
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.
aftables generates spreadsheets that meet the UK Analysis Function's accessibility guidance, taking structured input and producing a formatted workbook with cover, contents, notes and table sheets. Version 2.0.0 replaced the workbook engine with openxlsx2 and added configuration through a config.yaml file, with create_config_yaml() exporting a template and generate_workbook() gaining arguments to point at it. The package was previously called a11ytables and was renamed in 1.0.2, with function names changed to match.
The history reads in two phases. As a11ytables the work was about what belongs in an accessible spreadsheet, adding arbitrary pre-table metadata rows and enforcing rules such as rejecting tab titles that start with a numeral. Since the rename the work has been structural: a new backend, and configuration moved out of function arguments into a file that can be version-controlled and shared across a team. That second phase suits the audience, since government analysts producing recurring statistical releases want the same document properties applied every time rather than re-specified per run.
Expect the config.yaml surface to grow to cover more of what is currently passed as arguments, given it arrived alongside alternative author, title and keywords arguments that it plainly supersedes. With the openxlsx2 migration complete, further releases are likely to be formatting fixes surfaced by real departmental publications, as 2.0.1 already was.
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.
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.
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.
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 aftables or surveycore.
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 aftables alternatives → · See all surveycore alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. aftables 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. aftables 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.
Top aftables alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "aftables alternatives" section above for the current picks, or visit /alternatives/aftables for the full list with editorial commentary on each.
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.