3 ms·
Because once they open that can of worms they're on the hook for supporting it. Additionally, there isn't a good way out on the browser side, as Vulkan/DX12/Me
by monocasa 8y ago
Because once they open that can of worms they're on the hook for supporting it. Additionally, there isn't a good way out on the browser side, as Vulkan/DX12/Metal style APIs would pretty trivially allow JS code to escape whatever sandbox it's in. So the obvious answer is to keep their OpenGL implementation internal to Safari, and only support one of the new APIs (obvs Metal in this case) for native apps.
- iainmerrick 8y agoWhy would the web need Vulkan-style APIs? It just needs WebGL (so far). I still don’t see why that Safari implementation of OpenGL would have to stay internal.
- favorited 8y ago> Why would the web need Vulkan-style APIs For the record, there is an Apple-led initiative to bring a modern GPU interface standard to the browser: https://webkit.org/blog/7380/next-generation-3d-graphics-on-the-web/ https://webkit.org/blog/7380/next-generation-3d-graphics-on-...
- iainmerrick 8y agoI hope there’s no plan to drop WebGL. Although it wouldn’t surprise me. Really the only question is when -- years or decades?
- pjmlp 8y agoThey are all (Apple, Mozilla, Google, Microsoft) collaborating on the WebGLNext design, as Khronos decided to leave it up to W3C. https://www.w3.org/community/gpu/ https://www.w3.org/community/gpu/