I will merely throw in secondary comments because Paul and Robert have said
many of the major points.

I welcome our new direct-state overlords. I think OpenGL NG could be a
great idea. Apple and AMD have clearly seen the light with their own Mantle
and Metal efforts and Microsoft has been pushing this way with DX12. But
they are likely to suffer NIH-syndrome because no competitor wants to sign
on to an API that their opponent controls completely  (cf CUDA, DirectX,
etc).

I too, am wary of past failures like Fahrenheit and the original OpenGL 3.
But recent events (these new APIs, the change in market share to OpenGL ES
devices) have changed a lot of the landscape. Perhaps today they can
succeed where they failed in the past, if properly supported. I suspect
Microsoft might even have a teeny bit of interest in it, but they are so
internally conflicted that who knows. The fact that they are shipping
Office for iPad is a sea change over there and Satya Nadella could be the
difference.

Robert, what you describe as LSG sounds VERY much like the JAG project Paul
has been working on for a couple of years. Right down to the using OSG as a
transitional loader. JAG currently works pretty nicely with OpenGL 4 and
OpenGL ES, leaving out support for legacy/FFP features and leveraging
mature modern library dependencies (BOOST, POCO, GL3W, GMTL).

I can't comment on how JAG's current architecture might map to a NG API,
especially since we have no idea what that API might be. But I think it's
probably adaptable to it somehow, and is a good base to work from in the
future.

I am actually excited about the future potential of the OpenGL NG API. I
hope it goes good places and I'm looking forward to going there with it.

​
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to