There are many safe programming languages that do not rely on extra safety features of the hardware. Calling it "false promise that will be exploited and unfixa

There are many safe programming languages that do not rely on extra safety features of the hardware. Calling it "false promise that will be exploited and unfixable" is not supported by the evidence. That is to say, WebGPU is working with IHVs indirectly via Khronos, Microsoft, etc, and is putting pressure to introduce the safety features at the driver/hardware level. We've been arguing for more defined UB in Vulkan specs, initialization of workgroup memory, device memory ownership, and other things.