I'm not aware of the context here but that sounds like an interesting story. Could you give more details or do you know where I could read more about this?
When Apple decided to make their own GPU, all the other GPU vendors sued them for patent infringement. Apple countersued, and the litigation went on for many, many years. In the case of Nvidia there were also previous legal disputes over liability for Macbook GPU hardware defects, which meant that Apple had cut all ties with Nvidia years prior. This probably led to Apple's legal fight with Nvidia being especially prolonged and vicious.
Khronos Group, which produces the OpenGL and Vulkan standards, has ties to Nvidia. I don't know all the details but it seems Apple's lawyers decided that they would block implementation of any new Khronos standards in Apple products due to the Nvidia connection. As a result the OpenGL implementation in macOS was frozen at 4.1 for many years (dating from 2010 and lacking compute shaders), even prior to deprecation. Of course Vulkan support for macOS was completely out of the question. They also stopped work on Safari's implementation of WebGL 2 (which was left in a half-done state for years until it was eventually pushed to completion by Google engineers including myself). Additionally, Apple successfully maneuvered the WebGPU working group out of Khronos to W3C, and vetoed SPIR-V on the web, eventually resulting in WGSL.
So the legal dispute between Apple and Nvidia had a big influence on the industry. If Apple hadn't been allergic to Khronos standards, in an optimistic scenario we might have had a significantly better Vulkan standard with contributions from Apple's Metal team, Vulkan+SPIR-V support on macOS and iOS, and even SPIR-V on the web, which would have given us a truly cross-platform modern graphics API to replace OpenGL and made writing portable graphics software significantly easier in the last decade.
Of course today all this seems a lot less relevant with the rise of coding agents that can port a codebase or even a binary executable between platforms with a few prompts. So it will soon be a forgotten historical curiosity.
Secondly, thanks to extension spaghetti from Khronos APIs, the portability across devices, OS and computing platforms is hardly much different than coding to multiple graphics backends.
There are hardly any Khronos APIs related content at game conferences, that isn't done by Khronos themselves.
So even without coding agents it has never been that industry relevant, other than on open source communities.
I see this pattern again and again. For example in the manufacturing industry there’s a network standard OPC UA. It sucks. It tries to extend to absolutely everything (wtf database interfaces?). Like you say, the “integrators” just write a middle layer and move on with their days.
Point is, the reasons we didn't get any even minimally portable native graphics API this cycle are more legal than technical.
Anything else is just fine using the OS visualisation widgets on their UI toolkits, and if portability is that much of a concern, pick Qt, wxWidgets or whatever, already solved in the 1990s.
Also, not having a regression test that catches OpenGL being completely broken on many common hardware configurations seems pretty bad. Yes, OpenGL on macOS is deprecated, but guess what, deprecating it was also stupid. It was a legal decision made by Apple lawyers pursuing a particular litigation strategy vs Nvidia that caused Apple's withdrawal from Khronos group. It wasn't a sound technical decision.
Both of these things make it seem like the lawyers are in charge at Apple rather than the engineers.