Hacker News Reader

Interesting. The OpenGL team used to be one of the most prominent driver teams at IMG, and now it's outsourced. They explain the (market) reasons in the post.

View on HN

I am not surprised. As I understand it, Vulkan is a low-level API which is a much better fit to the actual hardware than OpenGL or DirectX.

You probably want to implement Vulkan anyways, so why bother re-implementing a separate legacy API when an existing translation layer can give the same or better result for a fraction of the effort? Heck, Intel even did the same thing to get DirectX working on their Arc GPUs: they just used Wine's DXVK translation layer.

Note that Intel is only using a translation layer for DirectX 9, and from what I’ve heard online the result is bad performance. DirectX 11 and 12 are both implemented natively.

DirectX 11 and 12 are both much more aligned to the hardware. DX 12 took the basic principles from AMD's Mantle and is very similar to Vulkan and Apple's Metal. Therefore, it makes a lot of sense and is not too much additional work to implement these natively.

More like it brought to DirectX PC, most of the stuff that was already available in XDX.

Intel are actually using Microsoft's D3D9on12, which isn't nearly as good as dxvk.

I believe they're using both. Swapping depending on the game.

https://www.tomshardware.com/news/intel-gpu-driver-optimizat...

Reply on news.ycombinator.com