← Back to home
Comparison · Infra & APIs

Skipper vs waldo

A side-by-side editorial comparison of Skipper and waldo — release velocity, themes, recent moves, and the top alternatives to consider.

Skipper vs waldo: at a glance

FeatureSkipperwaldo
SectorInfra & APIsInfra & APIs
Velocity score5.00.0
Sparks · 30d00
Top themeshttp-routing, load-balancing, observability, kubernetes-ingresstesting, diffing, dependencies, s7
Last editorial update12h ago2h ago
WebsiteVisit →Visit →

What is Skipper?

Skipper tags a release per commit, and this time one of them is a new load-balancing algorithm.

Zalando's HTTP router publishes a GitHub release for essentially every merged commit, so the feed reads as a commit log: doc corrections, dependency group bumps and small refactors each get their own version tag. Underneath that noise, v0.27.53 adds leastRequests, a load-balancing algorithm that routes to the endpoint with the lowest inflight-requests-to-weight ratio and breaks ties with smooth weighted round-robin. The surrounding releases are documentation for data client latency metrics, a jwtValidation behaviour clarification, and a Valkey ratelimit refactor.

Read the full Skipper trajectory →

What is waldo?

waldo keeps shedding dependencies while teaching its diff engine new object systems

waldo produces the object comparisons that testthat failure messages are built from. The recent releases do two things: drop dependencies - tibble, rematch2 and fansi have all gone - and extend comparison to object systems that did not exist when it was written, notably S7. Correctness of missing-value and tolerance semantics accounts for most of the rest.

Read the full waldo trajectory →

Skipper vs waldo: editorial side-by-side

S
Skipper
INFRA · APIS
5.0

Skipper tags a release per commit, and this time one of them is a new load-balancing algorithm.

◆ Current state

Zalando's HTTP router publishes a GitHub release for essentially every merged commit, so the feed reads as a commit log: doc corrections, dependency group bumps and small refactors each get their own version tag. Underneath that noise, v0.27.53 adds leastRequests, a load-balancing algorithm that routes to the endpoint with the lowest inflight-requests-to-weight ratio and breaks ties with smooth weighted round-robin. The surrounding releases are documentation for data client latency metrics, a jwtValidation behaviour clarification, and a Valkey ratelimit refactor.

◆ Where it's heading

The routing layer is getting more load-aware. leastRequests picks endpoints by observed inflight load rather than by position or hash, which suits backends with uneven per-request cost — and it arrives alongside newly documented route-sync latency metrics, so both the routing decision and the route-loading path are becoming measurable. The dependency and CI churn filling the rest of the feed is automated maintenance on a mature proxy, not a signal about direction.

◆ Prediction

Expect leastRequests to pick up tuning as production traffic exercises it, and the release-per-commit tagging to continue burying that kind of change among doc fixes. Whether it becomes a recommended default over roundRobin is not something these entries indicate.

W
waldo
INFRA · APIS
0.0

waldo keeps shedding dependencies while teaching its diff engine new object systems

◆ Current state

waldo produces the object comparisons that testthat failure messages are built from. The recent releases do two things: drop dependencies - tibble, rematch2 and fansi have all gone - and extend comparison to object systems that did not exist when it was written, notably S7. Correctness of missing-value and tolerance semantics accounts for most of the rest.

◆ Where it's heading

This is a package deliberately shrinking its footprint while widening what it understands. Since it is imported by testthat, every dependency it drops is one fewer package in the check environment of most of CRAN, which is clearly the motivation. The comparison logic itself changes only when R gains a new way to represent objects.

◆ Prediction

Expect S7 support to deepen from basic to complete as S7 adoption grows, and further dependency removals; the diff algorithm itself looks settled.

Alternatives to Skipper and waldo

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 Skipper or waldo.

See all Skipper alternatives → · See all waldo alternatives →

Recent activity from Skipper and waldo

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoSkipperNew leastRequests load balancer routes by inflight load factor
  2. 1d agoSkipperMarkdown list formatting fix in the docs
  3. 1d agoSkipperDocument data client route-sync latency metrics
  4. 2d agoSkipperPin oras-go to a released version to satisfy osv-scanner
  5. 3d agoSkipperClarify jwtValidation behavior after a proposed advisory
  6. 3d agoSkipperRefactor Valkey Del and ratelimit ring client injection
  7. 1y agowaldoCompares weakrefs, ignores read-only S7 properties
  8. 1y agowaldoOnly uses bit64 comparison when bit64 is installed
  9. 1y agowaldoDrops tibble and rematch2; adds basic S7 support
  10. 1y agowaldoDrops the fansi dependency
  11. 2y agowaldoFixes for upcoming R-devel changes
  12. 3y agowaldoTolerance now governs both display and NaN equality

Frequently asked questions

What is the difference between Skipper and waldo?

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 Skipper better than waldo?

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 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.

What are the best alternatives to waldo?

Top waldo alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "waldo alternatives" section above for the current picks, or visit /alternatives/waldo for the full list with editorial commentary on each.