The Docker+WASM Technical Preview
docker.com
The Docker+WASM Technical Preview
1–10 of 178 posts
Re: The Docker+WASM Technical Preview
#2Insert "BUT WHY?" GIF here.
Seriously, if you're in a position to be running native code in your environment why would you chose WASM? If you're building WASM for the web, is it really more expensive to build a pure native target out of the same source? Surely, performance wise you'll always be ahead going native.
Re: The Docker+WASM Technical Preview
#3Insert "BUT WHY?" GIF here. Seriously, if you're in a position to be running native code in your environment why would you chose WASM? If you're building WASM for the web, is it really more expensive to build a pure native target out of the same source? Surely, performance wise you'll always be ahead going native.
The same reason you're using Docker itself
Re: The Docker+WASM Technical Preview
#4Michael Irwin from Docker here (and author of the blog post too). Happy to answer your questions, hear feedback, and more!
Re: The Docker+WASM Technical Preview
#5Insert "BUT WHY?" GIF here. Seriously, if you're in a position to be running native code in your environment why would you chose WASM? If you're building WASM for the web, is it really more expensive to build a pure native target out of the same source? Surely, performance wise you'll always be ahead going native.
Put simply, more powerful isolation than Docker (with explicit, granular managed effects), and a simpler operating model, i.e. no container orchestration. You can actually compile modules from disparate stacks that call into one another in a single runtime.
Re: The Docker+WASM Technical Preview
#6Great work, WASM is the future!
But on the other hand I'm not really happy with the fact that I'm waiting for GC and DOM access since 2019 or something like that
and it doesn't seem like we're getting close
Re: The Docker+WASM Technical Preview
#7Michael Irwin from Docker here (and author of the blog post too). Happy to answer your questions, hear feedback, and more!
What problem is this solving?
Re: The Docker+WASM Technical Preview
#8Michael Irwin from Docker here (and author of the blog post too). Happy to answer your questions, hear feedback, and more!
maybe a naive question: is there a way to run some form of docker in the browser? It could be a great education / demo tool
Re: The Docker+WASM Technical Preview
#9Apologies in advance for a bit of a rant, but I sincerely hope the tools growing up around WASM significantly diminish the need for Docker. As an industry, we're so bad at isolation that we have to put a computer (container) inside a computer (VM) inside a computer (hardware) just to achieve any sort of sane guarantees.
Then we immediately trade any semblance of sanity for container orchestration.
(And please don't try to convince me that Kubernetes is sane. I operated a production SaaS on it for 4 years, and spent another year at a DevSecOps consultancy with 40+ CKAs—sanity and familiarity are not the same.)
Re: The Docker+WASM Technical Preview
#10Great work, WASM is the future! But on the other hand I'm not really happy with the fact that I'm waiting for GC and DOM access since 2019 or something like that and it doesn't seem like we're getting close
They just want to protect the frontend from the C#/Java crowd.