I'd like that, but I've decided it's not my battle. Reading some other threads, the consequences of monolithic legacy ICDs sunk in. Retaining all that backwards compatibility is expensive. It means that development of newer stuff I want doesn't get done, like an actually standard Khronos blessed wrapper library on Windows. DX gets far more testing because it's got the critical mass now, not OpenGL. So the OpenGL drivers are buggy and give game developers fits. I don't need this. I will do my next project in DX11 and worry about porting when and if it makes money. By then, maybe I'll be more impressed with the OpenGL situation; I am not today.Originally Posted by V-man
Bet they, and you guys, pay more attention if I become rich. As is, I'm just one voice among the many, that they've all heard before. If I become rich, will I care about this anymore? If I make enough money with DX11, will I need to bother with cross-platform anything? Maybe I'll prefer to work on game AIs or game designs or whatnot. Who knows.Go to their website and see if there is a contact.
Or visit http://www.opengl.org/registry/
there are emails of driver developers in each extension. Those guys play a role in the ARB.
Here's what I suggest you guys do instead, the ones that have a reason to care about OpenGL, that want to see it prosper. All you extension wrapper writing guys, sit down in one place, and SOLVE THE EFFING PROBLEM. Not to denigrate anyone's individual work, but you are past a point of software engineering where your divided efforts simply don't matter anymore. Most people can't / won't spend a week looking at the gory details of all your libraries to decide whether you did it right or not. Progress "in the large" requires people to combine resources and standardize. It should be a SDK, it should be unit tested, it should have automated nightly builds, it should be the only entry displayed on the opengl.org web menu. Whatever you do, make the whole thing MIT licensed. Don't GPL the generator code. Believe it or not, commercial entities want to modify the entire wrapper generation process. They don't want to be stuck with just your .h output.
If you guys can't work together or simply don't care to, then why would you expect much more out of Khronos? They don't have a lot of money to pay people to work together, so they have to contend with design-by-committee politics as well. You can spend time with an email campaign trying to convince them, or you can write it up yourselves.
Hmm, this sounds familiar. Did I write something like this around here a few years ago? Maybe it was for something else, with the same political dimensions. Anyways, good luck. I'll take a look at OpenGL again in a year or two.