3 ms·

Like you said - Microsoft is just completely passive regarding Vulkan on Windows. It's up to the GPU vendors and driver makers, as long as DirectX isn't threate

Like you said - Microsoft is just completely passive regarding Vulkan on Windows. It's up to the GPU vendors and driver makers, as long as DirectX isn't threatened. And on Xbox, DirectX is your only option, so if you want a nice clean Windows to/from Xbox port, writing for DirectX just makes sense. As for #2, Qualcomm (according to new reports) has an exclusivity deal for Windows on ARM that is expiring soon. But Microsoft would have to work with Apple and allow drivers to be written for the M1. Craig Federighi of Apple said they would be fine with Windows on M1 but Microsoft wasn't at the time. Though, to be honest, even if the exclusivity deal expires, I don't see Microsoft being excited about Windows on the M1. It only serves to embarrass their own products.

DCKing 5y ago
> But Microsoft would have to work with Apple and allow drivers to be written for the M1. Yeah to be fair I don't actually think that's going to happen. Someone needs to bear the burden of developing/maintaining a Windows graphics driver for Apple Silicon, which is a huge task. (Other drivers too, but that's not quite the same expense.) Apple will almost certainly not pay for that, and Microsoft would have to be extremely committed to having their OS be sideloaded on a competitor's devices to do it. If either Apple or Microsoft does do it though, you can be pretty sure you won't be seeing any Vulkan drivers soon.