rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of bulkreadr and surveycore — release velocity, themes, recent moves, and the top alternatives to consider.
A bulk file reader became a labelled-survey-data toolkit, then went quiet
bulkreadr started as a way to read many files at once and turned into tooling for labelled survey data: SPSS and Stata importers that convert labelled variables to factors, generate_dictionary() for building data dictionaries, look_for() for searching variable descriptions, and imputation helpers. The most recent release does the opposite of adding — it pulls inspect_na() in-house to drop an external dependency.
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.
bulkreadr started as a way to read many files at once and turned into tooling for labelled survey data: SPSS and Stata importers that convert labelled variables to factors, generate_dictionary() for building data dictionaries, look_for() for searching variable descriptions, and imputation helpers. The most recent release does the opposite of adding — it pulls inspect_na() in-house to drop an external dependency.
Growth came in a burst across 2023, slowed to one release a year, and has now turned inward. The 2023 cadence added a format or a labelled-data function every few weeks; 2025 added a single Excel-to-CSV exporter; 2026 removed a dependency. The GitHub notes are cumulative — each release restates every prior version's changelog — which makes the feed look busier than the work is.
With inspectdf gone, the remaining Suggests-level dependencies are the obvious next targets for the same treatment. Nothing in these entries points to a new file format or a return to the 2023 pace.
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 bulkreadr 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 bulkreadr 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. bulkreadr 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. bulkreadr 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 bulkreadr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "bulkreadr alternatives" section above for the current picks, or visit /alternatives/bulkreadr 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.