Contrary to FOSS beliefs, consoles never had proper OpenGL support anyway, so game studios already had to take care of multiple APIs on their engines.
https://www.youtube.com/watch?v=VZ0aWbZjX6M
https://www.youtube.com/watch?v=eX5hUdhI4Hs
https://dl.dropboxusercontent.com/spa/9hdhy0x8uk9d155/02uwwr...
https://dl.dropboxusercontent.com/spa/9hdhy0x8uk9d155/iwy2qc...
It does run both in Safari and WebView and it's pretty fast:
http://blog.ludei.com/webgl-ios-8-safari-webview/
http://www.photonstorm.com/html5/a-first-look-at-what-ios8-m...
It has very decent subset of features supported:
https://www.dropbox.com/s/i80qxzap59i230n/2014-06-02%2023.43...
But apparently it's not yet fully stable.
Also Dean Jackson from Apple's WebGL team tweeted, please direct eventual bug reports to him:
I can't see Khronos making the same fuck up twice, as they did with Longs Peak.
Yeah, it means depreciating a bunch of 3.x shit, and probably making another profile, but this time they better do it right.
2 years? in two years time nvidia will have their next line of GPUs out (pascal), intel will have launched knights landing (the many core xeon), and the next version of OS X will be released. 2 years is a long time, and it will already be behind the curve from it's announcement. khronos have a history of stagnation and disappointment.
> I can't see Khronos making the same fuck up twice, as they did with Longs Peak.
i think you may be mis-under-estimating khronos..
The problem with OpenGL is legacy code and committee hell.
If something works, like precompiled shaders, OpenGL committee will include it in the future spec.
I use OpenGL for very simple things, OpenGL needs to loose weight and get slim. I am certainly not satisfied with OGL 2.1. It is a design that does not make sense anymore with actual hardware(it did like 10 years ago).
I like the general trend indicated by this and Mantle and DX12, but the return to full-on platform fragmentation is a bit depressing.
Not a bad bet, if you ask me...
Independent dev writing low poly apps for multiple platforms is the Unity use case.
OpenGL 2.1 will be supported forever, don't worry, since you don't need anything more than GL2.1 it will run everywhere.
OpenGL isn't exactly a product. There's no company that "writes" the OpenGL software. Rather, it's a specification published by a consortium. "Writing" the OpenGL libraries is a task that each GPU maker does independently. So you have a bunch of different implementations of the same API.
For a long time, GPU makers have focused their attention on DirectX and done a lackluster job with their OpenGL implementations. If APIs like DirectX and Metal continue to proliferate, there will be less and less time and less incentive to maintain a good OpenGL implementation.
The fragmentation of OpenGL is enough of a headache, but at least it offers some semblance of "write once, run anywhere." The introduction of Mantle and Metal, plus the longstanding existence of Direct3d, makes me worry that OpenGL will get no love. And then we'll have to write our graphics code, three, four, or goodness knows how many times.
I know: It's not realistic to expect "write once, run anywhere" for any app that pushes the capabilities of the GPU. But what about devs like me (of whom there are many) that aren't trying to achieve AAA graphics, but just want the very basics? For us, "write once, run anywhere" is very attractive and should be possible. I can do everything I want with GL 2.1, I don't need to push a massive number of polys, I don't need a huge textures, and I don't need advanced lighting.