Simplifying Vulkan One Subsystem at a Time
Summary
The Khronos blog post argues that Vulkan’s extension-rich ecosystem leads to an “extension explosion” and proposes a radical approach: replacing entire subsystems with new, self-contained extensions. The first concrete example is VK_EXT_descriptor_heap, which fully replaces the existing descriptor set subsystem, enabling a memory-based descriptor model closer to console-style APIs. The post discusses the rationale, collaboration, and the plan to release as an EXT for early adoption before (potentially) moving to a KHR core, inviting community feedback to refine the approach.