The Docker+WASM Technical Preview
11–20 of 178 posts
Re: The Docker+WASM Technical Preview
#12Apologies 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 t…
I don't remember exactly when he says it's time to get rid of containers and VMs, but it's in there...
https://www.destroyallsoftware.com/talks/the-birth-and-death...
Re: The Docker+WASM Technical Preview
#13Re: The Docker+WASM Technical Preview
#14Michael 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?
As far as Wasm itself, it's designed to provide a fast, lightweight, secure, and portable binary format. While it was originally designed to help bring native code to the browser, it's quickly spreading to the server side. Many folks are using it for edge/IoT, but it's growing into other areas (saw demos today of even using it in databases as psuedo stored procedures). Happy to dive in more if you have more questions!
Re: The Docker+WASM Technical Preview
#15Apologies 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 t…
I know this wasn't your main point, but if I could reasonably tattoo this onto my forehead I would.
Re: The Docker+WASM Technical Preview
#16Apologies 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 t…
Re: The Docker+WASM Technical Preview
#17Earlier quoted context omitted.
What problem is this solving?
Depends on which "this" you're referring to. We (Docker) are trying to make it easier for developers to use the tools and capabilities they know and love to build, share, and run Wasm applications. As far as Wasm itself, it's designed to provide a fast, lightweight, secure, and portable binary format. While it was originally designed to help bring native code to the browser, it's quickly spreading to the server side.…
Re: The Docker+WASM Technical Preview
#18Michael 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
But... certainly a neat idea to think about what Wasm-based applications could possibly look like/run in the browser!
Re: The Docker+WASM Technical Preview
#19Great 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
#20Great 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.