4 ms·

Ready-to-use python.wasm, also in a Docker+Wasm container image.

• still_grokking 4y ago
  But please don't forget to wrap it in at least some VM! /s That's not even funny, as in real life people would run something like that actually in a VM. So we have now: HW memory protection -> HW virtualization -> VM -> OS -> Docker -> WASM -> language runtime -> some code snippet. Things become quite crazy these days, to be honest…
  • assambar 4y ago
    I totally agree with you on how ridiculous this is. But it's all about trade offs in the end. In the case of Docker+Wasm you get portability and delivery speed. You build one image for the wasm32/wasi platform and now it can run on any architecture that has Docker, just like that. And also you don't carry the whole OS baggage of a typical container. Only the language runtime. So download times are faster. --- Lastly, the Docker deployment is just the easiest way for a WASM application to reach people. They can try it out without the necessity to setup and support a WASI runtime.