We were expecting a lot from OpenGL
opengl 3, and as you can tell by reading this article, we’re disappointed—both in the API itself (with the disappearance of promised features) and in the way it’s been handled (a year-long delay and a lack of clear communication on the part of the Khronos group). With this version, OpenGL barely keeps up with Direct3D
direct3d 10, and at a time when Microsoft has chosen to publicize the first details of version 11 of its own API.
There’s nothing revolutionary from Microsoft either, but unlike OpenGL, Direct3D already underwent a major revision of its architecture two years ago. There were some rough stretches of road, but today Microsoft can reap the benefits of the efforts made then to rebuild the API on a sound foundation.
So, it’s undeniable that Redmond is looking to the future, whereas one gets the impression that Khronos is content with just supporting current GPUs. Here’s hoping it’ll prove us wrong by speeding up the evolution of OpenGL 3, since it is the only API available for multi-platform development. But too many letdowns up until now certainly have our faith in the organization shaken.