humind
The MSNI humanitarian needs framework as code, rewritten and re-broken every year
Comparison · Infra & APIs
microViz vs Skipper
A side-by-side editorial comparison of microViz and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.
microViz vs Skipper: 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 Skipper?
Skipper trims a 4x memory regression out of routesrv, days after shipping h2c
Zalando's HTTP router ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.63, which stops routesrv holding an uncompressed route tree alongside the compressed buffer: retained memory in the release's own benchmark falls from 30.7 MB to 2.0 MB, undoing most of the 4x increase zone-aware routing had introduced. Around it sit narrow auth repairs, and an eskip parser change that finally accepts negative numeric arguments in predicates and filters.
microViz vs Skipper: 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.
Skipper
5.0INFRA · APIS
Skipper trims a 4x memory regression out of routesrv, days after shipping h2c
◆ Current state
Zalando's HTTP router ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.63, which stops routesrv holding an uncompressed route tree alongside the compressed buffer: retained memory in the release's own benchmark falls from 30.7 MB to 2.0 MB, undoing most of the 4x increase zone-aware routing had introduced. Around it sit narrow auth repairs, and an eskip parser change that finally accepts negative numeric arguments in predicates and filters.
◆ Where it's heading
Two threads run through the recent tags. The data path keeps getting real work - leastRequests balancing, then h2c end to end in v0.27.57, now the memory cost of zone-aware routing being paid back. The auth filters, by contrast, are only being maintained: token introspection, grant auth, and now the OIDC Referer handling are fixes rather than new capability, and several are follow-ups to each other rather than independent bugs.
◆ Prediction
Zone-aware routing looks like the source of the recent memory attention, so expect further tuning around route storage and the hash computation done on every pull, which the release's second benchmark already isolates. The OIDC cookie change is the second link in an auth chain that started with the grant-auth fix, and is likely to draw another follow-up.
Alternatives to microViz and Skipper
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 Skipper.
inlabru
A Bayesian spatial modelling package rebuilding its foundations one breaking release at a time
afcharts
UK government chart styling in ggplot2, chasing ggplot2 v4 and stretching its palette to five.
coga
A gamma-convolution density package that reached completion in 2018 and has coasted since.
smam
Animal-movement models in R, where new stochastic processes arrive years apart.
baseq
A basic DNA and RNA sequence toolkit that went quiet for three years, then jumped to 2.0.
See all microViz alternatives → · See all Skipper alternatives →
Recent activity from microViz and Skipper
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 20h agoSkipperMove OIDC flow protection from Referer to cookies
- 20h agoSkipperv0.27.63: Store routes compressed-only, decompress on demand (#4198)
- 1d agoSkipperEskip predicates and filters accept negative numbers
- 1d agoSkipperFix token introspection handling
- 1d agoSkipperFix grant auth flow
- 2d agoSkipperUpdate outdated golang.org/x dependencies
- 3mo agomicroVizmicroViz 0.13.1
- 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 Skipper?
They serve adjacent needs but don't currently overlap on shipped themes. Skipper is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is microViz better than Skipper?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Skipper is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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 Skipper?
Top Skipper alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Skipper alternatives" section above for the current picks, or visit /alternatives/skipper for the full list with editorial commentary on each.