← Back to home
Comparison · Infra & APIs

aftables vs surveycore

A side-by-side editorial comparison of aftables and surveycore — release velocity, themes, recent moves, and the top alternatives to consider.

aftables vs surveycore: at a glance

Featureaftablessurveycore
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesaccessibility, spreadsheets, government-statistics, openxlsx2survey-statistics, variance-estimation, replicate-weights, api-stability
Last editorial update4h ago1h ago
WebsiteVisit →Visit →

What is aftables?

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.

Read the full aftables trajectory →

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.

Read the full surveycore trajectory →

aftables vs surveycore: editorial side-by-side

A
aftables
INFRA · APIS
0.0

Accessible government spreadsheets in R, rebuilt on openxlsx2 and renamed along the way.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

S
surveycore
INFRA · APIS
0.0

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 aftables 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 aftables or surveycore.

See all aftables alternatives → · See all surveycore alternatives →

Recent activity from aftables and surveycore

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 2mo agosurveycoreFirst stable release: all four survey design types complete
  2. 3mo agosurveycoreget_effective_n() computes effective sample size
  3. 3mo agosurveycoreCollections error on divergent grouping; .on_missing renamed
  4. 4mo agoaftablesrlang import restored for older R versions
  5. 4mo agosurveycoreCRAN patch removing surveytidy from the vignette
  6. 5mo agoaftablesWorkbook engine moved to openxlsx2; config.yaml introduced
  7. 1y agoaftablesPackage renamed from a11ytables to aftables
  8. 2y agoaftablesTab titles beginning with a numeral now rejected
  9. 2y agoaftablescustom_rows allows arbitrary pre-table metadata
  10. 2y agoaftablesTable count spelled out; README spelling corrected

Frequently asked questions

What is the difference between aftables and surveycore?

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.

Is aftables better than surveycore?

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.

What are the best alternatives to aftables?

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.

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.