← Back to home
Comparison · Infra & APIs

ggalign vs surveycore

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

ggalign vs surveycore: at a glance

Featureggalignsurveycore
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesggplot2, layout, heatmaps, s7survey-statistics, variance-estimation, replicate-weights, api-stability
Last editorial update52m ago3h ago
WebsiteVisit →Visit →

What is ggalign?

Composable aligned layouts, rebuilt on S7 while ggplot2 4.0 lands underneath.

ggalign composes multiple ggplots against a shared observation ordering, covering heatmap annotation, oncoplots, phylogenies and circular layouts. Releases have come roughly monthly through 2025, first completing the layout system, then migrating the internals to S7 and absorbing the ggplot2 4.0 changes. The alignment machinery is now exported for other packages to build on.

Read the full ggalign 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 →

ggalign vs surveycore: editorial side-by-side

G
ggalign
INFRA · APIS
0.0

Composable aligned layouts, rebuilt on S7 while ggplot2 4.0 lands underneath.

◆ Current state

ggalign composes multiple ggplots against a shared observation ordering, covering heatmap annotation, oncoplots, phylogenies and circular layouts. Releases have come roughly monthly through 2025, first completing the layout system, then migrating the internals to S7 and absorbing the ggplot2 4.0 changes. The alignment machinery is now exported for other packages to build on.

◆ Where it's heading

Two threads run in parallel. One widens what can be aligned, with sector facets, ideograms, image point shapes and observation linking. The other keeps rebuilding the foundation, with the S7 migration, repeated renames toward consistent naming, and the deliberate handing of element_polygon() and element_curve() upstream to ggplot2. The renaming is aggressive enough that each recent release soft-deprecates something.

◆ Prediction

With the internals on S7 and the Patch object exported, the next step is most likely stabilising those names rather than another refactor.

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

See all ggalign alternatives → · See all surveycore alternatives →

Recent activity from ggalign 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 agosurveycoreCRAN patch removing surveytidy from the vignette
  5. 10mo agoggalignalignpatch internals moved to S7; Patch object exported
  6. 11mo agoggalignInternals migrated to S7; ideogram, tags and image shapes
  7. 1y agoggalignz aesthetic scales and guide collection in borders
  8. 1y agoggalignchannelGrob() draws across facets; ggplot2 3.5.2 fix
  9. 1y agoggalignLayout system declared complete; polar facets and coord_circle()
  10. 1y agoggalignLayouts split into discrete and continuous; linking system added

Frequently asked questions

What is the difference between ggalign and surveycore?

They serve adjacent needs but don't currently overlap on shipped themes. ggalign 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 ggalign better than surveycore?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ggalign 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 ggalign?

Top ggalign alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ggalign alternatives" section above for the current picks, or visit /alternatives/ggalign 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.