That seems to give way too little credit to Mantle. Which was released in 2013 and became the basis for Vulkan.
I also noted that AMD donated Mantle as the starting point which is why Vulkan didn't take 5 years to finalize.
In any case claiming that Apple is somehow at fault for not adopting Vulkan doesn't make sense.
I just said that it's severely overstating the case.
> In any case claiming that Apple is somehow at fault for not adopting Vulkan doesn't make sense.
Why not? They could have adopted Mantle instead, for example. It came out a year earlier. Or it could have replaced Metal with Vulkan later (as it is often a reasonable choice to replace your custom solution with the industry's standard). Or it could have chosen to officially support Vulkan alongside it.
Apple has lots of money in the bank, and with that, lots of options.
Metal is the reason Vulkan exists: Apple announced Metal in June 2014 and the first Khronos meeting about a replacement for OpenGL was hosted at Valve in July 2014 so they could rush to announce an "open standard" under development at SIGGRAPH later that year. The only reason it managed to ship a final spec in 2016 was because AMD donated Mantle to boot-strap the process.
When you make your own GPUs and have sufficient scale to get developer adoption owning your own API can let you move much faster than others while avoiding vendor extension hell (that turns into a bespoke API-within-an-API at the extreme end).
Besides which MoltenVK effectively allows Vulkan software to run against Metal anyway. In that sense it's also better for Vulkan because it can ship API updates whenever Khronos feels like it.