rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of fastpos and surveycore — release velocity, themes, recent moves, and the top alternatives to consider.
Dormant three years, then a two-line release nobody using it would notice
fastpos finds the critical point of stability for a Pearson correlation, a simulation problem whose C++ implementation is the entire reason the package exists. Its substantive work concluded in 2022 with 0.5.0, the release prepared during R Journal review, which renamed the precision parameters, moved multicore work to pbapply and let users set corridor limits directly. After three years of silence, 0.6.0 removes an internal restriction to cpp11 and changes index_pop to an integer.
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.
fastpos finds the critical point of stability for a Pearson correlation, a simulation problem whose C++ implementation is the entire reason the package exists. Its substantive work concluded in 2022 with 0.5.0, the release prepared during R Journal review, which renamed the precision parameters, moved multicore work to pbapply and let users set corridor limits directly. After three years of silence, 0.6.0 removes an internal restriction to cpp11 and changes index_pop to an integer.
This is a finished piece of research software in low-effort upkeep. The changelog's centre of gravity is the R Journal review process, and once that concluded the package stopped changing. The single release since is toolchain work of the kind that keeps a package compiling rather than anything a user would see.
Expect nothing beyond occasional compilation or CRAN-check fixes unless the accompanying paper draws requests for other correlation types or resampling schemes.
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.
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 fastpos or surveycore.
The recursive-computation engine under massProps grows the accessors its consumer needed
A mass-properties rollup spends a year on documentation and follows its sibling's API
Six months of releases and not one of them touched the scoring models
A cognitive-science sampling package ships once, then goes quiet for eighteen months
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
See all fastpos alternatives → · See all surveycore alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. fastpos 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. fastpos 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.
Top fastpos alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "fastpos alternatives" section above for the current picks, or visit /alternatives/fastpos for the full list with editorial commentary on each.
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.