Or why you don't insist in using Khronos stuff on Windows, when most OEMs only care about the native API, DirectX.

Lets recap that this lesson has been learned by Godot developers, regarding their backends as well.

The ICD mechanism is a kind of escape hatch leftover due to backwards compatibility, and even user mode drivers build on top of DirectX runtime infrastructure.

▲

leecommamichael a day ago | parent [-]

Is it Khronos? The 3 issues they linked were: 1. ARM support missing for one of their Cargo crates. 2. An issue with RemoteDesktop 3. The team required dynamic_rendering, and it wasn't available for user with an old machine on Windows 10.

It really depends how you define scope, but I don't think I would've taken on another GPU backend for that.

	▲	pjmlp a day ago \| parent [-]
		In the sense that OpenGL and Vulkan are paper standards that OEMs might implement, whereas they tend to design their DirectX drivers alongside Microsoft, and then their OpenGL/Vulkan drivers are mostly an afterthought. This is especially visible when buying random asian cards that aren't the reference designs from AMD and NVidia. Intel was never great regardless of the API. Additionally we have the usual extension spaghetti, which is one thing that has beaten them here. Require too many of them, and coding around their inexistence becomes like using yet another API, that is similar but not quite.