I agree with the nit. > Simply put – Apple doesn’t need to care about Vulkan or OpenGL performance. OpenGL and Vulkan allow an implementer to more easily make

I agree with the nit. > Simply put – Apple doesn’t need to care about Vulkan or OpenGL performance. OpenGL and Vulkan allow an implementer to more easily make such specialized HW. But it doesn't assume it at all in any other way. If your HW is fast enough there is absolutely no need to implement specialized block for it without any performance penalty. It's trivial to implement things like input assembler without specific HW, just issue loads. But it would be massive pain to go the other way around. Try to sniff what loads fit the pattern that could be tossed into fixed function input assembler. That's a no go. This is the right way around to do things. As there is no performance penalty for "emulating" it, because there is nothing to emulate in the end.