3 ms·
> Ship to Mobile, Desktop, Servers and WASM all with one code base. Dumb question: what would a WASM implementation be useful for? Browsers don't expose "raw"
by xg15 7y ago
> Ship to Mobile, Desktop, Servers and WASM all with one code base.
Dumb question: what would a WASM implementation be useful for? Browsers don't expose "raw" TCP or UDP connections, so even if you have a fully working WebRTC implementation in WASM, there would be no way to connect to anything when ran inside a browser.
Or is this for WASM use outside the browser?
- microcolonel 7y agoPeople are building server-side WASM runtimes, which I suspect is your answer. To me the other answer is they could provide the same API in the browser through a shim.