3 ms·
It'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-h
by Muromec 2y ago
It'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.