rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
Comparison · Infra & APIs
Cobbler vs surveycore
A side-by-side editorial comparison of Cobbler and surveycore — release velocity, themes, recent moves, and the top alternatives to consider.
Cobbler vs surveycore: at a glance
What is Cobbler?
A backport branch kept alive for downstreams, with the main line nowhere in sight.
Every release in Cobbler's visible history describes itself the same way: backports from main to make Cobbler more stable for the community. The 3.3.x line has absorbed real work under that framing — collection indices, lazy loading, new XML-RPC endpoints — but none of it originates here. The most recent item is a 3.2.3 build carrying the CVE-2024-47533 fix to an older branch, with its Fixed and Added sections left as literal TBD placeholders.
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.
Cobbler vs surveycore: editorial side-by-side
Cobbler
0.0INFRA · APIS
A backport branch kept alive for downstreams, with the main line nowhere in sight.
◆ Current state
Every release in Cobbler's visible history describes itself the same way: backports from main to make Cobbler more stable for the community. The 3.3.x line has absorbed real work under that framing — collection indices, lazy loading, new XML-RPC endpoints — but none of it originates here. The most recent item is a 3.2.3 build carrying the CVE-2024-47533 fix to an older branch, with its Fixed and Added sections left as literal TBD placeholders.
◆ Where it's heading
This is a stabilization branch serving downstream packagers rather than a product advancing on its own. The work that does land splits cleanly into three buckets: distribution coverage (Ubuntu 22.04, Debian 12, AlmaLinux, RHEL9, openSUSE and SLE signatures), API surface for integrators, and security backports. 3.3.3 flagged dump_vars as the replacement for get_blended_data as of 3.4.0 — a version that has not appeared in any release since.
◆ Prediction
Expect continued single-purpose backports to 3.3.x and older branches as CVEs surface; the entries give no indication of when or whether the 3.4.0 work these releases keep deferring to will ship.
surveycore
0.0INFRA · APIS
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 Cobbler 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 Cobbler or surveycore.
massProps
A mass-properties rollup spends a year on documentation and follows its sibling's API
writeAlizer
Six months of releases and not one of them touched the scoring models
samplr
A cognitive-science sampling package ships once, then goes quiet for eighteen months
stochvol
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
midr
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
See all Cobbler alternatives → · See all surveycore alternatives →
Recent activity from Cobbler and surveycore
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoCobblerCobbler 3.2.3 backports the CVE-2024-47533 admin API fix
- 2mo agosurveycoreFirst stable release: all four survey design types complete ⚡
- 3mo agosurveycoreget_effective_n() computes effective sample size
- 3mo agosurveycoreCollections error on divergent grouping; .on_missing renamed
- 4mo agosurveycoreCRAN patch removing surveytidy from the vignette
- 1y agoCobblerCobbler 3.3.7 closes an admin-API authentication bypass
- 2y agoCobblerCobbler 3.3.6 adds EFI support to buildiso
- 2y agoCobblerCobbler 3.3.5 adds collection indices and lazy loading
- 2y agoCobblerCobbler 3.3.4 extends packaging to Ubuntu 22.04 and Debian 12
- 4y agoCobblerCobbler 3.3.3 adds resolved-value XML-RPC endpoints for Uyuni
Frequently asked questions
What is the difference between Cobbler and surveycore?
They serve adjacent needs but don't currently overlap on shipped themes. Cobbler 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 Cobbler better than surveycore?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Cobbler 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 Cobbler?
Top Cobbler alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Cobbler alternatives" section above for the current picks, or visit /alternatives/cobbler 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.