Hacker News Reader

not sure what's the current status of Go so there are two alternatives:

if they are targeting Wasm pre Wasm-GC then they have to ship their GC in the Wasm module and it can't interoperate with "the outside world"

if they use Wasm-GC then they use the host's GC and values can be shared with the host and other guests.

No, Go can never use WasmGC because Go has interior pointers. Not even fat pointers help because Go has unboxed types.

Go will continue to use its own GC for the foreseeable future.

Interesting. Can it collect garbage _concurrently_ in WASM?

Last I checked WASM applications are single threaded, not sure if that's changed. GC is concurrent, but not parallelized.