WASM GC ISN'T READY FOR REALTIME GRAPHICS

Summary from the TLDR Web Dev newsletter

Wasm GC (GC = Garbage Collection) has performance drawbacks for real-time graphics programming. The core issue is the opacity of Wasm GC heap objects to the JavaScript host, requiring byte-by-byte data copying between Wasm and JavaScript for operations like WebGL rendering. This copying impacts performance, especially when handling large datasets, unlike the direct access offered by Wasm linear memory.