[Encounter]

Metal is by far a much friendlier API than Vulkan. Its approach with opt-in complexity is arguably the correct one. (Ever tried writing a Vulkan "Hello triangle" from scratch?)

It's also gaining some nice features that are usable out of the gate, rather than waiting on Vulkan extension standardization and adoption. It simply makes the most sense for Apple.

[capableweb]

> Metal is by far a much friendlier API than Vulkan

Sure, but that was hardly the point of Vulkan in the first place. The point is to have cross-platform 3D grahipcs, but since Apple never gave a shit about anything cross-platform, they chose to write their own stuff.

And if they actually did care, they could have modeled the same API as they have with Metal, but over Vulkan, so the engine is the same but the API is "much friendlier".

It simply makes the most business sense for Apple, but as is tradition, the whole software ecosystem is worse off because of their choices.

[Encounter]

Well you can use Vulkan over Metal with MoltenVK, so that point is a bit moot.

Opinion time: WebGPU will become the standard graphics API to target for cross-platform. gfx-rs/wgpu already works over Vulkan/Metal/D3D12/D3D11/OpenGL/WebGL & WebGPU in browsers. Much better than simply Vulkan, unless performance is your primary sticking point.

[pjmlp]

First they have to sort out what that frankenstein merge of C++, HLSL and Rust named WGSL is supposed to look like.

[capableweb]

How is the point of Apple pushing Metal instead of Vulkan when the change request submitted to Blender is not using the MoltenVK stuff you're talking about? If anything it proves my point