3 ms·
What about packaging & distribution? Unless I missed something, it's up to us to package & ship our app complete with assets. I firmly believe that this projec
by plq 8y ago
What about packaging & distribution? Unless I missed something, it's up to us to package & ship our app complete with assets.
I firmly believe that this project is incomplete without a standard like .war (Web ARchive, from the Java ecosystem).
Of course, you could just use what's out there eg. .app (macos) or .appimage (gnu/linux) but there has to be a well-defined and clearly endorsed way of distributing wasmer'd apps.
- tyfon 8y agoThis "ship all libraries in the package" approach is also quite scary, you never know if an app will use your patched local libraries or use an ancient library with lots of exploits. Double so for anything exposed to the internet.
- plq 8y agoWASM binaries needn't be exposed to the internet. That said, the OS-sanctioned runtime could very well support a shared-object-like approach instead of one-binary-per-app but that would 1. complicate the runtime quite a lot 2. hinder startup times of wasm apps due to dependency solving.