← Back to home
Comparison · Infra & APIs

nzilbb.vowels vs surveycore

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

nzilbb.vowels vs surveycore: at a glance

Featurenzilbb.vowelssurveycore
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themessociophonetics, linguistics, pca, r-packagesurvey-statistics, variance-estimation, replicate-weights, api-stability
Last editorial update51m ago2h ago
WebsiteVisit →Visit →

What is nzilbb.vowels?

A vowel-analysis package trimming dependencies after an email address got it archived.

nzilbb.vowels supports sociophonetic vowel analysis — principal component analysis over vowel measurements, Procrustes comparison of loadings, and the plotting that goes with them. Three releases are visible, all in the 0.4.x line and all small. The substantive thread is dependency removal: vegan and gghalves have both been dropped in favour of code the package controls.

Read the full nzilbb.vowels 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 →

nzilbb.vowels vs surveycore: editorial side-by-side

N
nzilbb.vowels
INFRA · APIS
0.0

A vowel-analysis package trimming dependencies after an email address got it archived.

◆ Current state

nzilbb.vowels supports sociophonetic vowel analysis — principal component analysis over vowel measurements, Procrustes comparison of loadings, and the plotting that goes with them. Three releases are visible, all in the 0.4.x line and all small. The substantive thread is dependency removal: vegan and gghalves have both been dropped in favour of code the package controls.

◆ Where it's heading

The package is reducing what it relies on, and paying for it in small interface breaks — plot_correlation_counts() lost its half_violin argument and gained a points argument in the same move. The 0.4.2 notes also record that version 0.4.1 was archived by CRAN because the maintainer's email had become unreliable, prompting a switch to an institutional address. That is administrative rather than technical, but it explains why three closely spaced patches exist at all.

◆ Prediction

With the two external plotting and ordination dependencies gone and the maintainer address stabilised, the visible pressure that produced these releases is resolved. Nothing in the entries indicates what comes next, and the history is too short to read a feature direction from.

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 nzilbb.vowels 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 nzilbb.vowels or surveycore.

See all nzilbb.vowels alternatives → · See all surveycore alternatives →

Recent activity from nzilbb.vowels 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. 8mo agonzilbb.vowelsnzilbb.vowels 0.4.3
  6. 8mo agonzilbb.vowelsnzilbb.vowels 0.4.2
  7. 1y agonzilbb.vowelsnzilbb.vowels 0.4.1

Frequently asked questions

What is the difference between nzilbb.vowels and surveycore?

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

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

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