Traefik
Traefik's 2.11 line spends August fixing the names it generates for Kubernetes resources.
A side-by-side editorial comparison of surveycore and vcfR — release velocity, themes, recent moves, and the top alternatives to consider.
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.
A genomics workhorse whose visible release feed stops dead in mid-2020.
vcfR reads, manipulates and visualises VCF files, the standard format for genomic variant calls, and bridges them into R population-genetics classes such as genind, genlight and DNAbin. The three entries available here all come from the first half of 2020 and stop there, so the feed shows the state of the package six years ago rather than today.
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.
vcfR reads, manipulates and visualises VCF files, the standard format for genomic variant calls, and bridges them into R population-genetics classes such as genind, genlight and DNAbin. The three entries available here all come from the first half of 2020 and stop there, so the feed shows the state of the package six years ago rather than today.
Within that window the direction is unmistakably consolidation, not growth. 1.9.0 pushed error handling down into the C++ layer that actually reads the VCF so failures surface earlier and shared files stop tripping a readability pre-check, tightened class checks, and added conversion options. The two releases after it exist only to keep pace with R 4.0.0 and dplyr 1.0.0. Any development after June 2020 is not visible in this feed, so the current trajectory cannot be read from it.
No prediction can be grounded in these entries — the feed has been silent for six years, which points at a stale or broken source rather than at a package that stopped.
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 surveycore or vcfR.
Traefik's 2.11 line spends August fixing the names it generates for Kubernetes resources.
nginx returns to feature work with PROXY v2 upstream writes, and quietly adds JSON to core.
ESPHome closes the 2026.8 cycle, but the release body is a bare link to the real notes.
The R phone-number package stopped only parsing numbers and started asking them where they are.
A Venn diagram package whose public release notes say almost nothing — including about its copyright cleanup.
A Shiny app for choosing the right ordinal test reached CRAN in a single 90-minute burst of tags.
See all surveycore alternatives → · See all vcfR alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. surveycore and vcfR 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. surveycore and vcfR 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 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.
Top vcfR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "vcfR alternatives" section above for the current picks, or visit /alternatives/vcfr for the full list with editorial commentary on each.