← Back to home
Comparison · Infra & APIs

aftables vs inlabru

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

aftables vs inlabru: at a glance

Featureaftablesinlabru
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themesaccessibility, spreadsheets, government-statistics, openxlsx2bayesian-modelling, spatial-statistics, r-package, api-consolidation
Last editorial update1h ago46m 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 inlabru?

A Bayesian spatial modelling package rebuilding its foundations one breaking release at a time

inlabru wraps INLA for spatial, point-process and latent-Gaussian models in R. It is mid-modernisation: since 2.12.0 cut the sp stack, each release has renamed part of the public surface, standardised how external packages attach custom mappers, or replaced internal machinery. 2.15.0 is the latest step, pairing a new predictor evaluation and linearisation implementation with broom's tidy(), glance() and augment() methods and four non-zero-truncated observation families.

Read the full inlabru trajectory →

aftables vs inlabru: 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.

I
inlabru
INFRA · APIS
2.5

A Bayesian spatial modelling package rebuilding its foundations one breaking release at a time

◆ Current state

inlabru wraps INLA for spatial, point-process and latent-Gaussian models in R. It is mid-modernisation: since 2.12.0 cut the sp stack, each release has renamed part of the public surface, standardised how external packages attach custom mappers, or replaced internal machinery. 2.15.0 is the latest step, pairing a new predictor evaluation and linearisation implementation with broom's tidy(), glance() and augment() methods and four non-zero-truncated observation families.

◆ Where it's heading

The arc is consolidation of the extension surface rather than expansion of the model catalogue. Every release adds mappers or families with one hand and removes a dependency, a re-export or a deprecated path with the other — plyr in 2.15.0, fmesher's Depends entry in 2.14.1, sp and ggmap in 2.12.0. The compatibility flag bru_compat_pre_2_14_enable and the temporary fm_int/fm_pixels re-exports show a maintainer sequencing breaks across releases instead of landing them together.

◆ Prediction

The 2.14 compatibility flag is still defaulting to TRUE and the fmesher re-exports are described in the entries as temporary, so the next obvious move is a release that flips bru_compat_pre_2_14_enable off and drops those re-exports.

Alternatives to aftables and inlabru

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 inlabru.

See all aftables alternatives → · See all inlabru alternatives →

Recent activity from aftables and inlabru

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

  1. 23d agoinlabruPredictor linearisation rewritten; broom tidiers, truncated families
  2. 3mo agoinlabruBugfix release: factor contrasts, raster extraction, error classes
  3. 4mo agoaftablesrlang import restored for older R versions
  4. 5mo agoaftablesWorkbook engine moved to openxlsx2; config.yaml introduced
  5. 5mo agoinlabruNew mappers, standardised cgeneric support, bru_obs storage refactor
  6. 1y agoinlabruMapper classes shortened to bm_*, experimental predictor aggregation
  7. 1y agoaftablesPackage renamed from a11ytables to aftables
  8. 1y agoinlabruDrops sp and ggmap for an sf-native spatial stack
  9. 2y agoaftablesTab titles beginning with a numeral now rejected
  10. 2y agoaftablescustom_rows allows arbitrary pre-table metadata
  11. 2y agoaftablesTable count spelled out; README spelling corrected

Frequently asked questions

What is the difference between aftables and inlabru?

They serve adjacent needs but don't currently overlap on shipped themes. inlabru is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is aftables better than inlabru?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. inlabru is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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 inlabru?

Top inlabru alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "inlabru alternatives" section above for the current picks, or visit /alternatives/inlabru for the full list with editorial commentary on each.