4 ms·
>build a new low overhead close to the metal API and implement OpenGL on top of that This is a great idea and it should happen, but a Khronos committee is not
by modeless 12y ago
>build a new low overhead close to the metal API and implement OpenGL on top of that
This is a great idea and it should happen, but a Khronos committee is not the right place to do it. The only way it could end well is if the API is first designed and implemented outside of Khronos and Khronos's only role is to standardize it with minimal changes. For example, if Khronos decides to adopt Mantle as the basis for this new API, with a few changes to make it generalize better to all vendors' hardware, then that would be a good outcome. I fear that politics may not allow something like that to happen, and that's why I think a more incremental approach is better, but perhaps I'm too pessimistic.
- exDM69 12y ago> This is a great idea and it should happen, but a Khronos committee is not the right place to do it I'm afraid that Khronos is the only entity that can possibly do something like this. However, as you suggest it might be possible that the basis of a new API is one of the new proprietary APIs like Mantle or Metal. You seem to have some kind of dislike for Khronos but I don't think there is any better entity out there. The problem with Khronos is that it's understaffed and underfunded and for many of the people doing the hard work it's their secondary job.
- iandanforth 12y agoI hope that someone is either Facebook/Occulus or Google.