5 ms·
WebGPU doesn't necessarily mean "in the browser" though Rust game engines are using it as a library for native games
by anentropic 4y ago
WebGPU doesn't necessarily mean "in the browser" though
Rust game engines are using it as a library for native games
- pjmlp 4y agoIt does, anywhere else is better served with middleware that has full exposure to native 3D APIs without the constraints of an API designed to be called in a browser sandbox.
- habitue 4y agoWebGPU makes cross-platform seamless because it's got multiple backends, and it's quite capable. It can be extended to add native platform features
- pjmlp 4y agoThat is what middleware engines already do, and with much better tooling. WebGPU's place is on the Web, no need for more extension spaghetti than Khronos already do by themselves.
- anentropic 4y agoare you confusing it with WebGL? we're talking about https://github.com/gfx-rs/wgpu https://github.com/gfx-rs/wgpu which has Vulkan, Metal and DX12 backends
- pjmlp 4y agoNope, https://www.w3.org/TR/webgpu/ https://www.w3.org/TR/webgpu/