2 ms·
Having researched WebGPU a little, I'm not seeing anything there that explains why this over WebGPU. As far as I understand, those reasons are identical to thos
by bmitc 3y ago
Having researched WebGPU a little, I'm not seeing anything there that explains why this over WebGPU. As far as I understand, those reasons are identical to those for WebGPU.
Can anyone explain?
- jayd16 3y agoIs Android support solid for Dawn/webgpu? Seems like it's marked as work in progress compared to the confident support laid out here.
- adamnemecek 3y agoRight but if they needed that, they could have just contributed android support to wgpu.
- swatcoder 3y agoMeta has bet the farm on their VR/AR/XR platform and smartly wants control over the tooling that developers will use to target it. The last thing they want is for some Quest innovation to be hamstrung waiting for a standard body to approve support for some new feature or for a third-party open source maintainer to incorporate some fix/addition/compatibility PR. Owning a project like this, if they can get developers to use it, is a huge business security asset and competitive advantage for them. That's why this exists and why it's being promoted. Whether developers see it as worth using instead of other options is a different question. Meta would probably say the answer to "why" for developers is: "to make sure your project gets the most out of the Quest products (as well as other Android platforms), now and in the future"
- adamnemecek 3y agoThey can’t get users to use it as it provides little over webgpu.