Khronos Group announces Vulkan 1.1, the first big update to its cross platform GPU API, with multi-GPU support, better DirectX compatibility, and more
Peter Bright / Ars Technica :
Context & Ripple Effects
Vulkan has been building toward this since Khronos released the 1.0 specification in February 2016 as the successor to OpenGL, with Android committing early as the open counterweight to Metal and DX12. Days before this announcement, Khronos extended the API to Apple platforms through a collaboration with Valve, LunarG, and The Brenwill Workshop, giving the standard a fresh reason to move fast.
The 1.1 update is the first major revision of that 2016 baseline, and its headline additions — multi-GPU support and improved DirectX compatibility — target exactly the friction points that kept large codebases on vendor-specific APIs.
First-order effects
- Developers porting engines across Windows, Linux, Android, and the newly supported macOS/iOS targets get one current specification instead of per-platform forks, with multi-GPU workloads addressable through Vulkan rather than vendor extensions.
- Projects written against DirectX gain a cheaper migration path via the improved compatibility layer, lowering the switching cost that has favored staying on Microsoft's API.
Second-order effects
- Microsoft faces pressure to keep DirectX differentiated beyond familiarity, since the compatibility gap that anchored PC development to its stack narrows with each Vulkan release.
- Apple's closed graphics ecosystem now has an open-standard alternative maintained by Khronos and partners like Valve, giving macOS and iOS developers an option that does not depend on Apple's own API cadence.
Third-order effects
- If the cadence holds — from the 1.0 spec through the Apple port to 1.1 and later into shared AR/VR standards like OpenXR — Khronos is positioning itself as the neutral layer beneath platform vendors' proprietary graphics and spatial-computing APIs.
- Sustained cross-vendor convergence would shift competitive leverage from whoever owns the OS-level API toward whoever controls the tooling and runtime layers above the standard.
The trend: Open cross-platform GPU standards are expanding from mobile and PC into Apple and XR ecosystems, steadily eroding the moat around vendor-locked graphics APIs.