For decades, OpenGL has been a widely used and supported cross-platform graphics API. Each vendor has its own drivers, and these implementations have been developed and maintained with varying priorities, leading to a scenario where applications may run very differently based on whether the environment is Linux or Windows, x86 or Adreno, waxing or waning moon, etc.
This is not a good user experience, and it is not a tenable one for implementors either as companies and projects begin to reassign resources towards more modern APIs like D3D12 and Vulkan. What happens when the only OpenGL implementation for a platform has poor performance and lacks the engineers needed to repair it? What happens when new hardware is designed and there is no OpenGL implementation at all?
This is where Zink shines as a layered OpenGL implementation atop Vulkan. By having common codepaths used by all Vulkan drivers, a given platform needs only create a Vulkan implementation which satisfies the Zink feature requirements in order to gain a free OpenGL implementation--One that is, ideally, performant and correct on all systems in all scenarios.
This talk will explore the history and development progress of Zink, the current status, and plans for global OpenGL driver domination.
|GSoC, EVoC or Outreachy||No|
|Code of Conduct||Yes|
|In-person or virtual presentation||In-person|
|For which conference do you send the proposal?||X.Org Developers Conference 2022|