3 ms·
Yeh, this article kinda confirms what I've been thinking the past few years: "Implementing a server requires additional API functions exposed - specifically, s
by eyberg 6y ago
Yeh, this article kinda confirms what I've been thinking the past few years:
"Implementing a server requires additional API functions exposed - specifically, sock_bind, sock_listen, and sock_accept"
"And while implementing them is done similarly to what was described here so far, there is an underlying issue: there is no multi-threading support in WebAssembly"
Really surprised to see so many people talking this up to running many/most server-side applications with so many fundamental features missing.
- the_duke 6y agoThere is of course the threads proposal [1], which works in chrome with a feature flag, but most runtimes don't support it yet. In general I have to agree that WASM needs more time. There are multiple quite crucial proposals in the pipeline (reference types, interface types, threads, tail calls and other advanced control flow, module linking, (GC), ...) which have all seen very slow progress. Overall I'm still bullish on the potential of WASM for universal deployment, but the slow pace is a bit concerning. [1] https://github.com/WebAssembly/threads https://github.com/WebAssembly/threads