Many Web applications will just ship WGSL. This includes everything going through Three.js, Babylon.js, and hand-written web apps. It's not even clear if Chrom

Many Web applications will just ship WGSL. This includes everything going through Three.js, Babylon.js, and hand-written web apps. It's not even clear if Chrome or Firefox will accept SPIR-V binary as an extension at this point. Anyway, conversion to and from SPIR-V is supposed to be straightforward and light. Our (speaking for gfx-rs community) Rust-based shader infrastructure will handle that , and the converter should be easily compilable to wasm (when it's ready). Anyway x2, most of the time in the whole picture of creating pipelines will be spent in the driver, so whatever parsing performance difference WGSL brings to the table, be it 5% or 10%, doesn't matter, you aren't going to see that in benchmarks because of that other stuff that's going on when you are creating a pipeline.