>> One other important aspect is Metal implementation is much simpler than a Vulkan one – more on that later – so in some sense I’d prefer a Metal -> Vulkan wra

>> One other important aspect is Metal implementation is much simpler than a Vulkan one – more on that later – so in some sense I’d prefer a Metal -> Vulkan wrapper instead of a Vulkan -> Metal. Read this so often that it seems to be the consensus by now. I used to think "why doesn't Apple just hop on the Vulkan bandwagon and everyone will be happily united under one API", but given that Metal came before Vulkan, and it still has better DX, Apple was right. What excuse does Vulkan have being the second iteration on the same concept, but still be more tedious?