rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
Comparison · Infra & APIs
samplr vs surveytidy
A side-by-side editorial comparison of samplr and surveytidy — release velocity, themes, recent moves, and the top alternatives to consider.
samplr vs surveytidy: 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 surveytidy?
surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.
surveytidy is the tidyverse-facing half of a two-package survey stack, wrapping survey design objects from surveycore so filter, mutate, select and the rest work on them while carrying variable labels, value labels and a transformation log alongside the data. The May release extended that verb surface to survey_collection, the abstraction surveycore uses to hold several surveys as one object, so a pipeline written once dispatches across every member.
samplr vs surveytidy: 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.
surveytidy
0.0INFRA · APIS
surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.
◆ Current state
surveytidy is the tidyverse-facing half of a two-package survey stack, wrapping survey design objects from surveycore so filter, mutate, select and the rest work on them while carrying variable labels, value labels and a transformation log alongside the data. The May release extended that verb surface to survey_collection, the abstraction surveycore uses to hold several surveys as one object, so a pipeline written once dispatches across every member.
◆ Where it's heading
The package is being built in two layers that arrive in order: vector-level transformations first, structural dispatch second. The make_* family in 0.4.0 handles the recoding that survey work actually consists of — labelled to factor, multi-level to dichotomous, scale reversal, valence flipping — with value labels propagating automatically. Collection support then applies data-masking, tidyselect, grouping, slicing and collapsing verbs per survey, with joins explicitly refused and a typed message reporting which surveys were skipped. Metadata fidelity is the recurring bug source: labels surviving across(), stale labels left behind by recoding, the transformation log keeping up with what the verbs did.
◆ Prediction
Joins are the one verb family that errors on collections, with users directed to join before constructing the collection, so that restriction is the clearest outstanding gap. The re-export of surveycore's collection constructors suggests the package is positioning itself as the single import users need, which points toward more re-exports as surveycore's stable API settles.
Alternatives to samplr and surveytidy
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 surveytidy.
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
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
GeoThinneR
Spatial thinning grows a result object, and the API breaks to make room for it
See all samplr alternatives → · See all surveytidy alternatives →
Recent activity from samplr and surveytidy
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agosurveytidymutate() syncs metadata for across() recodes
- 3mo agosurveytidydplyr and tidyr verbs dispatch across survey collections
- 5mo agosurveytidyFive label-aware recoding functions for use inside mutate()
- 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 surveytidy?
They serve adjacent needs but don't currently overlap on shipped themes. samplr and surveytidy 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 surveytidy?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. samplr and surveytidy 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 surveytidy?
Top surveytidy alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "surveytidy alternatives" section above for the current picks, or visit /alternatives/surveytidy for the full list with editorial commentary on each.