&gt; which has tons of manpower behind<p>What is wrong with open-sourcing GC code as independent libraries, so that web-app makers or (more likely) compiler developers (with less skill&#x2F;time) can use them at will?<p>&gt;  the issue with #4 is that you would need threads w&#x2F; shared memory<p>But this is exactly what we need for other applications as well. For example, how would you send a large immutable data-structure across two threads? By copying it? Of course not, you just share pointers, meaning that the address space should be shared. If this is not possible, then that is a major flaw in WASM&#x27;s design.<p>I think you have the impression that incorporating a GC into WASM makes life easier. But it doesn&#x27;t. It is the exact opposite. WASM should be as simple as possible.