3 ms·
I see nothing silly about it. Bringing other bad examples of lock-ins doesn't excuse Apple in the least. Personally I'd stay away from the above too. > There's
by shmerl 2y ago
I see nothing silly about it. Bringing other bad examples of lock-ins doesn't excuse Apple in the least. Personally I'd stay away from the above too.
> There's also only a handful of Vulkan games
There are a ton of games that are Vulkan games through vkd3d-proton and dxvk. Which was the above point.
- flohofwoe 2y agoSo if Apple would provide a similar D3D shim on macOS, all D3D games would suddenly become "Metal games"? If Apple would implement Vulkan support on macOS it would be a layer on top of Metal (same as their GL implementation or MoltenVk). Running through two translation layers (D3D => Vk => Metal) doesn't make a lot of sense.
- deleted 2y ago[deleted]
- shmerl 2y agoSo it should be D3D → Vulkan → kernel / hardware. But Apple are too stuck up with their NIH to allow that.
- flohofwoe 2y agoThat would either mean that Apple needs to maintain two separate types of display drivers or create a new abstract driver interface which sits between Metal+Vulkan and the underlying hardware. That's just adding busywork with only downsides, both technical and organisational. Vulkan just isn't that important outside of Linux and Android, especially when most games are built on top of a crossplatform engine anyway.