Or it can be a very nice object based API instead of a state based API that made sense in 1992 as the slide deck said and certainly didn't make any sense in 2008 when the industry group Khronos sided with the commercial CAD industry to screw over Linux consumer gaming because there was no money in it. How was that DirectX's fault again?
I am guess you're not a game developer and your post is yet another case of [1].
I am a game dev and here are some links that show to non game devs why DirectX is more popular:
> Perhaps because design by a committee of peers usually results in a fragmentation and compatibility nightmare like this
It can. Or it can result in spec which helps everyone instead of just MS alone. Depends on how it's done. Vulkan is done from scratch, and so far I see no signs of them making mistakes of OpenGL. I guess we'll see more once it's released. Either way, what's the alternative? There is none, unless of course you work for MS and envision them controlling everything.
>Or it can result in spec which helps everyone instead of just MS alone.
Just MS alone? DirectX helps hundreds of millions of gamers, a whole bunch of game and application developers and companies.
That's like saying improvements to the Linux kernel help only the Linux kernel.
>Vulkan is done from scratch, and so far I see no signs of them making mistakes of OpenGL
Huh, how do you see that? The spec is developed behind closed doors by corporate folks each with their own interests. Even the W3C holds open discussions with specs.
A real alternative would be for the FOSS/Linux dev community to create and implement a standard properly.