3 ms·
You can't have dymanic linking of two C-like libraries compiled to wasm, because you would not be able to pass pointers around. Basically everything you compile
by Muromec 2y ago
You can't have dymanic linking of two C-like libraries compiled to wasm, because you would not be able to pass pointers around. Basically everything you compile to wasm becomes static binary which needs some bitfiddling to interact with.
- iforgot22 2y agoHm, so besides not having cross-site caching like ahoka mentioned, you can't even use some common fast CDN to host the compiled runtime.
- Muromec 2y agoIt's more of a go problem than the wasm problem. Don't bundle such a big runtime and pass memory pointers around and you can have nice things. Something beam-hosted with zero pointer sharing between nodes and smaller runtime maps to wasm much better.
- iforgot22 2y agoIt's also unfortunate for a lot of heavy JS libs out there that they can't be cached locally anymore, but security is important. One WASM-related case I've actually encountered in the wild is Unity web. Similar problem as Golang, the runtime is heavy.