Simple backoff ftw https://github.com/jpillora/backoff

That’s the exact same logic, just written more verbosely and excluding the actual retry mechanism.

They're different things, solving different problems:

- Containers are wrappers for binaries. Any binary can be contained, and when run, it gets a constrained (fake) view of the kernel.

- WASM defines a portable binary format. WASM is intermediate-representation, in the same vein as Java byte-code.

You could reasonably put WASM binaries inside containers

If you’re a Java dev, and you try to force Java-isms into Go, you’re gonna have a bad time.

The Go philosophy http://go-proverbs.github.io/ pays off less in the short term, within a single file, or a single stdlib function, or with syntactic sugar to code golf 3 lines into 1 - it pays off in the long term, across time and people - and this makes all the difference

See also https://github.com/jpillora/md-tmpl

Please make a live demo version of this using only JavaScript and HTML :D

RIP Stefan

You’re right, that’d be a better test - and I think the gap between chisel and crowbar would grow even more. Chisel is effectively doing ssh tunnelling, with extra layers. Performance is lost in packet wrapping/unwrapping, reduced MTU but it shouldn’t result in more round trips

Correct, it’s equivalent to ssh tunneling except there’s some HTTP/websocket wrappers around it

That’s exactly what it is, see releases

Tailscale is a virtual network device (works on L3, tun not tap device) whereas chisel just listens on ports (works on L4)