Conversation

I'd be more comfortable if they'd actually opened up the implementation of

@VulkanAPI

. Thankfully MoltenVK exists, and is OSS thanks to Khronos. No thanks to Apple though... 🙄😠

For those interested: github.com/KhronosGroup/M - here's hoping it works as advertised! If it does I really don't see any benefit at all to locking oneself into Metal at this stage.

Now, is there a good way to get this API running on WebGL?

I'm guessing Apple would have to keep OpenGL around in webkit. You can use MoltenGL if you still want to keep the same code between the web and your native build, but I believe that's still proprietary... moltengl.com/moltengl/

Webkit would most likely be doing something similar internally in the future. Will be interesting what the other browser engines will have to do to maintain WebGL compatibility on macOS...

Hopefully Apple makes this part of WebKit official supported as a gesture of good will. I mean we live in a world where Microsoft acquired github. Anything can happen.

Yeah, I'd hope. But Apple hasn't shown itself to be the same OSS steward like Microsoft has become. I mean, part of me is grateful that OpenGL is being deprecated - it's a terribly old, ugly API. The annoying thing is more that they haven't provided a standards-based alternative.

From what I hear it was a miracle of chance that we even ended up with a standardized cross platform graphics API that become somewhat popular. To expect it to happen a second time when everyone is incentivized against it might be too optimistic.

Don Olmstead

@don_olmstead

4:18 AM · Jun 5, 2018Twitter for iPhone

There’s WebGPU which you could probably build WebGL on top of webkit.org/blog/7380/next

Replying to

and

Ugh, you mean Apple’s attempt to prut Metal in the browser (as opposed to building an abstraction on top of Vulkan?)

Replying to

and

Actually Microsoft and Google are both involved is my understanding