[timanglade]

> I don't know any dev looking for this or having a problem solved by it.

Judging by the reception at KubeCon & elsewhere today, we think at least some folks are excited by it. But it’s still early, and who knows, you may be right in the end. We launched this as a technical preview to test a hypothesis and learn from it, and so far the interactions from this HN thread alone have been greatly helpful.

[heavyset_go]

Why were they excited? What use cases does this address?

Is the intention to containerize WASM binaries and manage them with Docker like you would any other container?

Genuine questions, I'm just trying to understand what this feature is and why someone would want to use it.

[timanglade]

I tried to answer this above[0]. Instead of trying to explain it again, I’d encourage you to give it a try[1], and if after going through the 5-minute tutorial you still don’t get the point then a) maybe we messed up (and I’ll be sorry for having wasted your time!) or b) maybe it’s not for you (and I’ll also be sorry I wasted your time). It took me a while to wrap my head around this Docker+Wasm thing too when I first heard about it internally — then again it took me months to wrap my head around my first demo of Docker, so maybe I’m just dense!

[0]: https://news.ycombinator.com/item?id=33324093

[1]: https://docs.docker.com/desktop/wasm/

[jammaloo]

As a heads up, the download links to the technical preview builds of Docker seem to be incorrect on that page https://docs.docker.com/desktop/wasm/. The Windows, Mac OS Intel and Silicon each point to https://www.docker.com/download/wasm-preview/linuxamd64deb which is the linux build.

The article linked by the OP has the correct links.

[heavyset_go]

Your second link answered my questions well, thanks.