humind
The MSNI humanitarian needs framework as code, rewritten and re-broken every year
A side-by-side editorial comparison of fio and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.
Input-output economics in R with a Rust core, now spanning multiple regions.
fio builds and analyses input-output models in R, using an R6 object for the model and Rust with the faer crate for the linear algebra behind technical coefficients and the Leontief inverse. Version 1.0.0 extended it from single-region tables to multi-regional models with spillover analysis, and 1.1.0 immediately corrected the naming and measures that release introduced, renaming shock-origin columns that had been labelled as destinations and replacing an interdependence index with spillover balance and export share.
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.
fio builds and analyses input-output models in R, using an R6 object for the model and Rust with the faer crate for the linear algebra behind technical coefficients and the Leontief inverse. Version 1.0.0 extended it from single-region tables to multi-regional models with spillover analysis, and 1.1.0 immediately corrected the naming and measures that release introduced, renaming shock-origin columns that had been labelled as destinations and replacing an interdependence index with spillover balance and export share.
The package built its foundation first and its scope second. The 0.1.x releases were almost entirely about making a Rust-backed R package install reliably across platforms and toolchain versions, with the actual economics settled at 0.1.0. Once that was stable, 1.0.0 added the multi-regional layer in one release, and 1.1.0 shows the usual consequence of a large surface arriving at once: names and derived measures needing correction before they harden. Breaking changes are being taken freely while the multi-regional interface is young.
Expect further refinement of the multi-regional measures before the interface settles, given that 1.1.0 revised them within three months of their introduction. The Rust core makes larger multi-regional systems tractable, so extending coverage to more published multi-region tables is the obvious direction, though these entries name no specific dataset.
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.
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.
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.
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 fio or Skipper.
The MSNI humanitarian needs framework as code, rewritten and re-broken every year
A Bayesian spatial modelling package rebuilding its foundations one breaking release at a time
UK government chart styling in ggplot2, chasing ggplot2 v4 and stretching its palette to five.
A gamma-convolution density package that reached completion in 2018 and has coasted since.
Animal-movement models in R, where new stochastic processes arrive years apart.
A basic DNA and RNA sequence toolkit that went quiet for three years, then jumped to 2.0.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
Top fio alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "fio alternatives" section above for the current picks, or visit /alternatives/fio for the full list with editorial commentary on each.
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.