Does WebGPU have Feature Parity with other Modern Graphics API's (Vulkan/DX12/Metal) #3804
TheFloatingBrain
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
A friend and I are considering using webgpu native (more specifically C++ bindings) for a project. We were wondering, since WebGPU likely runs on top of Vulkan XOR DirectX12 XOR Metal at any given time, and others have called it a "union" (interpreting the word in the set-theoretic sense) of the three if there were significant feature/functionality gaps with WebGPU as compared with these APIs? In other words, if Vulkan has a feature DirectX 12 does not or vise-versa, does WebGPU exclude it? What I am asking is: are there significant features (or functionality differences) these other APIs have, that WebGPU does not, or do they have feature parity?
Full disclosure I did also post this on a SE thread, but I thought I may get more WebGPU specialized knowledge here (especially since its relatively new)
Y'all seem to be doing great work! :)
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions