webgpu-headers

> Wgpu actually has C bindings to allow you to write C/C++ code with it, as well as use other languages that interface with C. That being said, wgpu is written in Rust, and it has some convenient Rust bindings that don't have to jump through any hoops. On top of that, I've been enjoying writing in Rust. Why the bloat when this exist? https://github.com/webgpu-native/webgpu-headers EDIT: nvm i got confused by the name.. who thought it was a good idea to have almost similar names?

> Google and Mozilla are also developing a C-compatible library that should be available as an OpenGL alternative for native code. To clarify, Google and Mozilla are both developing separate libraries: Dawn (in C++) and wgpu (in Rust) respectively. Both are designed to be usable behind the same native C API - https://github.com/webgpu-native/webgpu-headers > For the shading language they settled on a text based language designed to be easily translatable to/from Vulkan SPIR-V bytecode Going from SPIR-V has been anything but easy for us (in Naga/wgpu land), so far. Raph posted this link in the comment above - http://kvark.github.io/spirv/2021/05/01/spirv-horrors.html