rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
Comparison · Infra & APIs
microViz vs surveycore
A side-by-side editorial comparison of microViz and surveycore — release velocity, themes, recent moves, and the top alternatives to consider.
microViz vs surveycore: at a glance
What is microViz?
Microbiome ordination and visualisation, in maintenance and keeping pace with vegan and ggplot2.
microViz provides visualisation and statistics for microbiome data built on phyloseq, including ordination exploration, distance-based dispersion analysis and composition plots. The release notes are pointer-style entries that name a pull request and link a comparison range rather than describing what changed, so most of what can be established from this feed is cadence and dependency pressure rather than substance. Version 0.13.1 is the exception, naming documentation work on dist_bdisp and its defaults relative to vegan's betadisper.
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.
microViz vs surveycore: editorial side-by-side
microViz
0.0INFRA · APIS
Microbiome ordination and visualisation, in maintenance and keeping pace with vegan and ggplot2.
◆ Current state
microViz provides visualisation and statistics for microbiome data built on phyloseq, including ordination exploration, distance-based dispersion analysis and composition plots. The release notes are pointer-style entries that name a pull request and link a comparison range rather than describing what changed, so most of what can be established from this feed is cadence and dependency pressure rather than substance. Version 0.13.1 is the exception, naming documentation work on dist_bdisp and its defaults relative to vegan's betadisper.
◆ Where it's heading
Read through the dependency mentions, the pattern is a package spending its releases absorbing changes in the ecosystem beneath it: vegan deprecating summary in favour of scores, cowplot warning under ggplot2 3.5, testthat declarations centralised, CI actions updated. Nothing in the window indicates new analytical capability, and the 0.13.0 minor bump that would be the place to look for it ships with no notes at all. The honest reading is a stable package under maintenance by a single maintainer.
◆ Prediction
Expect continued upkeep against phyloseq, vegan and ggplot2 changes rather than a feature programme. Because the notes do not describe their own contents, a substantive release here would be indistinguishable from a maintenance one in this feed, so the direction cannot be read from these entries alone.
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 microViz 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 microViz 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 microViz alternatives → · See all surveycore alternatives →
Recent activity from microViz and surveycore
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agosurveycoreFirst stable release: all four survey design types complete ⚡
- 3mo agomicroVizmicroViz 0.13.1
- 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
- 6mo agomicroVizmicroViz 0.13.0
- 1y agomicroVizmicroViz 0.12.7
- 1y agomicroVizmicroViz 0.12.6
- 1y agomicroVizmicroViz 0.12.5
- 2y agomicroVizmicroViz 0.12.4
Frequently asked questions
What is the difference between microViz and surveycore?
They serve adjacent needs but don't currently overlap on shipped themes. microViz 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 microViz better than surveycore?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. microViz 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 microViz?
Top microViz alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "microViz alternatives" section above for the current picks, or visit /alternatives/microviz 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.