humind
The MSNI humanitarian needs framework as code, rewritten and re-broken every year
Comparison · Infra & APIs
echos vs Skipper
A side-by-side editorial comparison of echos and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.
echos vs Skipper: at a glance
What is echos?
Echo state networks for R forecasting, filling in the pieces a fable model is expected to have.
echos fits echo state networks, a reservoir-computing approach to time series forecasting, and exposes them through the fabletools model interface so they sit alongside other models in a fable workflow. The three releases in this window take it from a working model to a complete one: forecast intervals in 1.0.2, hyperparameter tuning by rolling-origin cross-validation in 1.0.3, and documentation covering the architecture, hyperparameters and tuning workflow in 1.0.4. Cadence is a few releases a year.
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.
echos vs Skipper: editorial side-by-side
echos
0.0INFRA · APIS
Echo state networks for R forecasting, filling in the pieces a fable model is expected to have.
◆ Current state
echos fits echo state networks, a reservoir-computing approach to time series forecasting, and exposes them through the fabletools model interface so they sit alongside other models in a fable workflow. The three releases in this window take it from a working model to a complete one: forecast intervals in 1.0.2, hyperparameter tuning by rolling-origin cross-validation in 1.0.3, and documentation covering the architecture, hyperparameters and tuning workflow in 1.0.4. Cadence is a few releases a year.
◆ Where it's heading
The arc here is a model implementation earning its place in an established framework. Point forecasts came first, then the interval forecasts that any fable-compatible model is expected to produce, generated by bootstrapping residuals and taking quantiles from simulated paths, then the tuning machinery that makes the reservoir hyperparameters usable by people who do not already know what alpha and rho do. Version 1.0.4 spending its whole release on documentation and a clearer dataset name is consistent with that: the remaining barrier is comprehension, not capability.
◆ Prediction
With intervals and tuning in place, the natural next step is broader integration with the fable ecosystem, such as handling multiple series or ensembling with other model types. The entries do not indicate whether the maintainer intends to go further into reservoir variants or to stabilise what is here.
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 echos 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 echos 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 echos alternatives → · See all Skipper alternatives →
Recent activity from echos 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
- 2mo agoechosDocumentation expanded; M4 dataset renamed
- 5mo agoechostune_esn() tunes reservoir hyperparameters by cross-validation
- 1y agoechosForecast intervals added via moving block bootstrap
Frequently asked questions
What is the difference between echos 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 echos 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 echos?
Top echos alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "echos alternatives" section above for the current picks, or visit /alternatives/echos 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.