In this context, what’s relevant is OpenXR. Apple’s visionOS does not natively support OpenXR, the open standard developed by the Khronos Group for cross-platform AR/VR development. Apple has not indicated any plans to adopt OpenXR, choosing instead to promote its proprietary frameworks such as ARKit, RealityKit, and PolySpatial for spatial computing on the Vision Pro.
What Apple is finding, however, is that there’s virtually no consumer or developer appetite for visionOS / Vision Pro.
> Hell would freeze over before Apple conformed and contributed to an existing open standard.
This is patently false given the fact I posted.
Now to add to the unhelpfulness in what I hope is a humorous way, we in fact have some evidence that hell did freeze over:
https://www.npr.org/sections/thetwo-way/2014/01/08/260735693...
It's a miracle they actually allowed Microsoft to be a member of the Khronos group.
I should try an make an image of Fahrenheit's beta cds some day.
From an article talking about their decision to build WebGPU[1]. I was definitely being dramatic, but do think that Apple's overall vibe doesn't mesh well with open standards.
Caniuse says it's still behind a feature flag, are you sure you didn't enable that at some point?
https://webgpu.github.io/webgpu-samples/?sample=texturedCube
So definitely not enabled by default yet.
WebGPU is still in progress in Safari - it is available as a technology preview. The same is true for Firefox.
That's kind of the point, Chrome shipped it across multiple platforms two years ago, while Safari still has no timeframe despite having a much narrower set of APIs and hardware to support. Firefox at least has the excuse of needing broad compatibility like Chrome but with a fraction of the development resources. Apple are just dragging their feet.
Chrome ships a lot of things. Even now WebGPU is marked as experimental technology on MDN.
WebGPU didn't even become a Candidate Recommendation until December 2024 (half a year ago)
> Apple are just dragging their feet.
Or they are not in any rush to implement APIs that haven't reached consensus, haven't passed reviews, are subject to change etc. Chrome has very very cavalier attitude towards shipping APIs.
Chrome has routinely shipped junk APIs with no concern for privacy, security or battery life.
It's why fingerprinting works so incredibly well on their browsers.
Why the vitriol?
Apple did in fact initiate and co-create the WebGPU standard [1].
[1] https://en.wikipedia.org/wiki/WebGPU
Edit to include quote of parent comment.