dkegel

FWIW the company I work for has been helping out a little here and there, one of our engineers has four commits in so far this year.

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.

There have been four committers in the last week, so it's active!

Consider joining the slack channel #tinygo-dev on gophers.slack.com and pinging them about the PR.

Another one was added an hour ago, https://github.com/tinygo-org/tinygo/pull/5280

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

Tinygo is supported by several edge computing platforms, and works well for at least one commercial application.

If you need wasm/wasi support, and you're ok with working around the partial support for reflect etc., it's not a bad choice.