How might WASM GC shipping to browsers affect the future of WASM Rust?

80 points nomyte

The Chrome dev blog announces WASM GC now being on by default. On a small benchmark, they report 6-9kb file sizes for C and Rust implementations and 2k for the same benchmark in Java.

How might the general availability of WASM GC affect the case for Rust as the "premier" source language for compiling to WASM in browsers?