3 ms·
This is the primary UX for Vulkan. The problem is not the API PDF for OpenGL you download from Khronos - its all the drivers that implement it. Not only do you
by zanny 11y ago
This is the primary UX for Vulkan. The problem is not the API PDF for OpenGL you download from Khronos - its all the drivers that implement it. Not only do you have to support he lowest common denominator GL version and then extension-check every higher level feature you want to use with two code paths every time, you also need to work around all the driver bugs you will find across the board with every combination of platform + GPU.
If OpenGL as of 4.5 were implemented perfectly on all hardware on all systems, we would never need Vulkan because everyone could just AZDO for optimization. Since we don't live in that fantasy world where pigs fly and Nvidia releases freedom respecting drivers, Vulkan takes responsibility away from hardware vendors who demonstrably cannot handle the work and puts the burden on the developer, who... probably also cannot handle the work, but thats a per-application problem rather than a fundamental API problem.
- Hello71 11y agoWhy couldn't someone write a "Vulkan backend for OpenGL" that combined proper standards conformance with actual hardware acceleration?
- zanny 11y agoYou can. Go ahead and do it. Mesa is likely to implement future OpenGL extensions by translating them to Vulkan rather than implementing them natively to the metal, and someone is probably going to make a libgl that targets Vulkan rather than any of the intermediary layers used around the ecosystem.