5 ms·
That's one of my big problems with WSL, and Microsoft's contributions to open source projects like Mesa. Their Dozen driver implements Vulkan on top of D3D12, a
by jakogut 4y ago
That's one of my big problems with WSL, and Microsoft's contributions to open source projects like Mesa. Their Dozen driver implements Vulkan on top of D3D12, a proprietary API only available officially on Windows. This is useless for anybody not using their proprietary software.
In my opinion, it should never have been accepted without an officially supported open source backend. I don't care if it's in the form of a Linux library, BSD, whatever, if it only adds value to your proprietary product, why should the open source community be shouldered with the burden of maintenance? Especially when _using_ said functionality locks users to your product.
Why didn't they use Vulkan for a backend, which is portable, well-supported, and open, and use and contribute to existing high quality drivers on top of it? There's only one reasonable answer, they're not interested in portability, working with the community, or omni-win-win scenarios.