Nextflow
Nextflow just made AI agents a task type, alongside processes and containers.
Comparison · Infra & APIs
samplr vs surveycore
A side-by-side editorial comparison of samplr and surveycore — release velocity, themes, recent moves, and the top alternatives to consider.
samplr vs surveycore: at a glance
What is samplr?
A cognitive-science sampling package ships once, then goes quiet for eighteen months
samplr compares human performance against sampling algorithms, giving cognitive scientists the MCMC machinery to test whether people behave like samplers. Its entire public history is three releases: a 1.0.0 in August 2024, a floating-point fix eighteen seconds later, and then nothing until a February 2026 patch. The release notes are unusually thin even by CRAN standards.
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.
samplr vs surveycore: editorial side-by-side
samplr
0.0INFRA · APIS
A cognitive-science sampling package ships once, then goes quiet for eighteen months
◆ Current state
samplr compares human performance against sampling algorithms, giving cognitive scientists the MCMC machinery to test whether people behave like samplers. Its entire public history is three releases: a 1.0.0 in August 2024, a floating-point fix eighteen seconds later, and then nothing until a February 2026 patch. The release notes are unusually thin even by CRAN standards.
◆ Where it's heading
The feed shows a package that shipped and stopped. The 2024 tags were both created in one sitting and say almost nothing; the 2026 release is a row-count bug in Mean_Variance() bundled with citation metadata, a dropped dependency and http-to-https link fixes — the housekeeping profile of a package being kept alive for the paper that cites it rather than actively developed.
◆ Prediction
Adding citation information to the README is usually the move of a maintainer expecting the package to be referenced rather than extended. On this cadence the next release is more likely another CRAN-hygiene patch than new algorithms; there is not enough in these notes to say otherwise.
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 samplr 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 samplr or surveycore.
dscore
The D-score reference implementation rebuilt its measurement foundation on seven countries.
ggfootball
A football-viz package just swapped scraping for an API and broke its own output to do it.
goat
A gene-set enrichment package that outgrew its human-only origins, then went quiet.
rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
massProps
A mass-properties rollup spends a year on documentation and follows its sibling's API
See all samplr alternatives → · See all surveycore alternatives →
Recent activity from samplr and surveycore
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 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
- 5mo agosamplrMean_Variance() row count corrected after eighteen months
- 1y agosamplrFloating point comparison fix
- 1y agosamplrsamplr 1.0.0
Frequently asked questions
What is the difference between samplr and surveycore?
They serve adjacent needs but don't currently overlap on shipped themes. samplr 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 samplr better than surveycore?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. samplr 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 samplr?
Top samplr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "samplr alternatives" section above for the current picks, or visit /alternatives/samplr 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.