Hacker News new | ask | show | jobs
by xg15 2244 days 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?
1 comments
microcolonel 2244 days ago
People 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.
link
fulafel 2244 days ago
It's the latter. See https://github.com/pion/webrtc/pull/479
link
xg15 2244 days ago
> they could provide the same API in the browser through a shim.

Oh, so in the browser, it would just fall back to the native WebRTC implementation? That would make sense.

link