WebAssembly architecture for Go
I'm trying to learn more about this topic and I'm curious if anyone could clarify for me -- 
The reason Go would need a specific architecture for WebAssembly is because Go supports features, like garbage collection, that WebAssembly does not.<p>Is that right? Close? An oversimplification. Way off?