OpenGL was released 29 years ago, and the way GPUs work now vs then is massive. Apparently developers want low level access, and that is what Vulkan/Metal give them.
As a user I wish Vulkan had a path without so much setup. I'm not sure if that's possible, or maybe it would defeat the purpose. It seems like it would be nice for hobbyists/beginners like me who just want to get a triangle on the screen and play with shaders though.
I understand that a lot of developers want low level access to hardware - that's great for a lot of applications. But that low level access means that software is tied to hardware... and software is not forward/cross compatible. Which is a VERY big deal for pro market.
Remember when Apple just "forgot" to release a pro grade desktop for years? Do you think those pros just stayed with their outdated hardware?(they didn't, they moved to Windows)
Do you think that there's a good reason for many pro software vendors to jump to Metal, when the majority of their customers are on Windows with Vulkan support?
I mentioned this on another subthread - Apple just needs to offer a cross platform API, to prove that they want pro software to be developed on Macs.
As a game dev - hardware dependence has been a fact of life for a very long time. There are too many useful extensions not included in the base profiles, and enough video cards combinatorically combined with those - that the most tractable path is to actually care about the specific device's capabilities.
The best way forward is to be as detailed as possible than to come up with a new albatross to hang around one's neck for the next 30 years. A thin driver with a fatter app stack is probably more manageable going forward than a very fat driver with a continually aging app stack, so long as appropriate care is paid to forward compatibility.
You have the benefit of abandoning your product 3-5 years after it's published, without anyone caring.
In 2011, Carmack would have gone with DirectX instead.
https://www.bit-tech.net/news/gaming/pc/carmack-directx-bett...
> The actual innovation in graphics has definitely been driven by Microsoft in the last ten years or so,' explained AMD's GPU worldwide developer relations manager, Richard Huddy. 'OpenGL has largely been tracking that, rather than coming up with new methods. The geometry shader, for example, which came in with Vista and DirectX 10, is wholly Microsoft's invention in the first place.' > > 'It is really just inertia that keeps us on OpenGL at this point,' Carmack told us. He also explained that the developer has no plans to move over to Direct3D, despite its advantages.
ARB, Long Peaks failure, not defining SDKs and leaving to ecosystem to create tools on their own, making into a rite of passage that each graphics programming student needs to create their own SDK from scratch, is anything but appealing.
If ARB/Khronos would standardize networking protocols, we would have only IP, and then each developer would create their own networking stack on top of raw IP.
Deprecating opengl was confusing for me.
That's why it must be deprecated. Why do we need to reinvent the wheel over and over again ? I get it, X sucks and the answer to this is .... wayland. OpenGL sucks and the answer to this is ? DirectX ? Vulkan ? SDL ? Libcaca ? ( sorry i forgot ncurses). Just like an old builder: you have some bricks, use them.