Is that a reason for us not to take you seriously? Feel free to disclose any connection you have with the subject but please don't disclaim responsibility for your comments. :)
Unless, of course, you want to..
(Sorry for the no-content post but I see this word used in every second thread these days and it's one of the things that might be driving me nuts.)
So, "disclaimer" is spot on, I believe, because application writers might like to shed a tear, but not sympathize too hard...
So, if that is the correct interpretation then is not a disclaimer, more a disclosure. Which is what noibl was trying to educate exDM69 about.
But it is really all idle speculation until exDM69 chimes in.
Yes. Someone should do it. The major industry players seem to have the interest but lack the will to put in the resources it requires.
> Right now I'm excited about OpenGL ES 3.0 for mobiles
Prepare for disappointment.
This means I am constantly really impressed by the fact that we get anything done at all.
Unfortunately, I am also a crazy arrogant monkey, so am also constantly really deeply disappointed by the fact that we haven't all got jet-packs and holiday homes on the moon yet.
Small nitpick: OpenGL would be catching up with Direct3d not with DirectX(which includes parts like input or sound that AFAIK are out of scope for OpenGL)
[1]http://programmers.stackexchange.com/questions/60544/why-do-...
edit: found HN discussion about this link: http://news.ycombinator.com/item?id=2711231
The main reason why OpenGL did not get a restart were because of pressures from CAD and 3D Modelling Industry.
These modern GPUs are very generalized hardware now. Their drivers are "simulating" all kinds of features. Its a bit like OSS vs ALSA. They should just make the GPU a standard compiler target, and offer only the bare minimum (video-mode-setting) at the driver level.
Let the game industry write/design their own API on top. Let the CAD community do the same for their usecases. I know, with Mesa, this is kind of the setup. Except mesa isnt executed by the gpu: it runs on the CPU, and from there it executes code on the GPU.
Wouldnt it be much nicer if GPUs just behaved like CPUs? They are just optimized for different types of proccesing. Thats the interesting end-game: could the CPU be optional?
And the CAD/DCC market gets a say because they pay 10-100x more per seat than consumers.
No, it is called the GL 4.2 core profile. GL 4+ core profile is a superset of GLES2. It does not include any of the stuff left behind from GL 1.x days.
GLES2, and Big-GL3+ have the legacy graphics features removed but the API is still horrible. More on this in my other comments in this thread.
http://www.jwz.org/blog/2012/06/i-have-ported-xscreensaver-t...
In any case, I submit to the opinion of experts - my experiments with OpenGL have been simple and, when I attempted anything more complicated, they resulted in much more frustration than learning.
fixed that for you.
I think what you meant is that OpenGL ES may one day be more popular and more used than the "full OpenGL", because there are a lot more mobile devices + WebGL.
On the other hand, porting from D3D code, you don't touch the hairy parts of OpenGL at all because D3D is functionally quite close to the "clean parts" of GL. But there's still some software overhead to overcome. They might also be using a proprietary D3D-on-OpenGL layer, like the ones being used for some Mac ports of Windows games (edit: seems like they are not).
I hope that Steam, and gamers that use Mac and Linux in general, will push for bigger changes in OpenGL, both specs and implementations.
disclaimer: I write GPU drivers for living