> Metal was released in June 2014[0], and Vulkan development started a month later, in July 2014[1]. > > You can interpret that in a few different ways There a

> Metal was released in June 2014[0], and Vulkan development started a month later, in July 2014[1]. > > You can interpret that in a few different ways There are no two interpretations. Metal was released before Khronos even had their "kick off meeting". The official introduction of Khronos didn't happen until 2015. Vulkan 1.0 was released in 2016. Prior to 2014 there was no Vulkan, and no idea of Vulkan. Sevral companies (AMD among them) tried to peddle their own proprietary APIs as a potential future direction after OpenGL. And yes, Khronos scrambled to have a modern API after both Microsoft and Apple ended up having one. > Yes, it took a further two years for any kind of reasonable Vulkan support to be out there No. It took two more years to just release version 1. And even in 2024 it's somewhat laughable to talk about "reasonable Vulkan support" when the major gaming platforms (Windows, Xbox, Playstation) don't support it (Windows supports DX natively, and Vulkan support is left to the whims of GPU vendors). The actual support for Vulkan is declining: https://carette.xyz/posts/state_of_vulkan_2024/ https://carette.xyz/posts/state_of_vulkan_2024/ > I think it's a bit disingenuous to say Apple was a trailblazer with absolutely no peer here. The trailblazer was Microsoft. What is disingenuous is to pretend that Vulkan was anywhere at the forefront or that Apple had to pay any attention to it, or that Apple is somehow in the wrong for not supporting it. > Hell, at this point, Vulkan might have seen more general adoption than Metal has. Of course it doesn't. Because iOS exists, supports Metal, and is a major gaming platform