4 ms·
If you ship an application using a native WebGPU library then you're in control of which implementation you use, unlike native APIs where you're at the mercy of
by jsheard 3y ago
If you ship an application using a native WebGPU library then you're in control of which implementation you use, unlike native APIs where you're at the mercy of the platform. It doesn't particularly matter if you use an extension that exists on Dawn but not on wgpu, if every build of your app comes packaged with Dawn.
- pjmlp 3y agoJust like any middleware engine, no added benefit, with less capable tooling.
- pcwalton 3y agoThe benefit of wgpu is that you don't have to mess with synchronization the way you do in Vulkan and DX12. This is an enormous productivity booster. Besides, if you pick one native API (say, Vulkan), then you're still going to go through translation layers on the platforms it isn't native to, so wgpu isn't any different. Or you can write multiple backends for different platforms, which multiplies the amount of work you have to do. Either way, saying that wgpu gives you "no added benefit" is silly.
- pjmlp 3y agoJust like middleware engines, with much better tooling.