[pancsta]

TinyGo doesnt have networking in WASI[0] and the WASM websocket module[1] was last updated 5 years ago. Go without stdlib is not Go.

[0] https://github.com/tinygo-org/tinygo/issues/4880

[1] https://github.com/Nerzal/tinywebsocket

[pjmlp]

Interestingly enough for the C and C++ folks, compiler specific dialects for embedded without standard library, are still argued for as if being C and C++.

[dkegel]

For embedded systems, see https://github.com/tinygo-org/net

For WASI, check out WASI Preview 2, https://docs.wasmtime.dev/api/wasmtime_wasi/p2/index.html

[pancsta]

Thats the host, but the guess is missing, as stated in the issue last year "I guess we could add sockets to wasip2". To be honest, even BigGo failed me on websocket conns on both wasmtime and wazero (connects and gets into an inf loop on reply). WebWorkers and GOOS=js work like a charm tho on BigGo in FF/chrome.

[dkegel]

Yeah, I suspect sockets in wasip2, and wasip2 in general, are just now having the bugs shaken out of them.

The company I work for is just now upgrading its edge WASI support to wasip2.