The generous interpretation is they just don't want to invest into that if it isn't "broken" but the cynic in me can't help but think at least part of the motivation is being different and maintaining the wall around the garden.
It's also gaining some nice features that are usable out of the gate, rather than waiting on Vulkan extension standardization and adoption. It simply makes the most sense for Apple.
Sure, but that was hardly the point of Vulkan in the first place. The point is to have cross-platform 3D grahipcs, but since Apple never gave a shit about anything cross-platform, they chose to write their own stuff.
And if they actually did care, they could have modeled the same API as they have with Metal, but over Vulkan, so the engine is the same but the API is "much friendlier".
It simply makes the most business sense for Apple, but as is tradition, the whole software ecosystem is worse off because of their choices.
Opinion time: WebGPU will become the standard graphics API to target for cross-platform. gfx-rs/wgpu already works over Vulkan/Metal/D3D12/D3D11/OpenGL/WebGL & WebGPU in browsers. Much better than simply Vulkan, unless performance is your primary sticking point.
Metal is the reason Vulkan exists: Apple announced Metal in June 2014 and the first Khronos meeting about a replacement for OpenGL was hosted at Valve in July 2014 so they could rush to announce an "open standard" under development at SIGGRAPH later that year. The only reason it managed to ship a final spec in 2016 was because AMD donated Mantle to boot-strap the process.
When you make your own GPUs and have sufficient scale to get developer adoption owning your own API can let you move much faster than others while avoiding vendor extension hell (that turns into a bespoke API-within-an-API at the extreme end).
Besides which MoltenVK effectively allows Vulkan software to run against Metal anyway. In that sense it's also better for Vulkan because it can ship API updates whenever Khronos feels like it.
That seems to give way too little credit to Mantle. Which was released in 2013 and became the basis for Vulkan.
I also noted that AMD donated Mantle as the starting point which is why Vulkan didn't take 5 years to finalize.
In any case claiming that Apple is somehow at fault for not adopting Vulkan doesn't make sense.
I just said that it's severely overstating the case.
> In any case claiming that Apple is somehow at fault for not adopting Vulkan doesn't make sense.
Why not? They could have adopted Mantle instead, for example. It came out a year earlier. Or it could have replaced Metal with Vulkan later (as it is often a reasonable choice to replace your custom solution with the industry's standard). Or it could have chosen to officially support Vulkan alongside it.
Apple has lots of money in the bank, and with that, lots of options.
The only cross platform alternative that actually works is OpenCL, but Blender is moving away from OpenCL, mostly because literally every GPU vendor is doing so as well.
The more annoying variation between the two is the need to refactor the code from using "kernels" to "compute shaders", but that's just a difference in the underlying programming model.
Yes, there is SPIR-V, yet few care to target it in practice, besides typical shading languages.
And why would they? OpenGL is really unpleasant from a hardware manufacturer's / integrator's / OS author's perspective, it makes app ports for mobile that much harder unless you're using GL ES, and Metal works and many apps have a Metal renderer now. If you find the mere idea of Metal distasteful because it's an API that can't be used on other platforms, you can use Vulkan and MoltenVK to get there.
You're confusing not caring for the pro market with their approach to vertical integration. They care for the pro market, but they're not willing to compromise on ripping out what they consider to be dead weight.
That's why it must be deprecated. Why do we need to reinvent the wheel over and over again ? I get it, X sucks and the answer to this is .... wayland. OpenGL sucks and the answer to this is ? DirectX ? Vulkan ? SDL ? Libcaca ? ( sorry i forgot ncurses). Just like an old builder: you have some bricks, use them.
OpenGL was released 29 years ago, and the way GPUs work now vs then is massive. Apparently developers want low level access, and that is what Vulkan/Metal give them.
As a user I wish Vulkan had a path without so much setup. I'm not sure if that's possible, or maybe it would defeat the purpose. It seems like it would be nice for hobbyists/beginners like me who just want to get a triangle on the screen and play with shaders though.
I understand that a lot of developers want low level access to hardware - that's great for a lot of applications. But that low level access means that software is tied to hardware... and software is not forward/cross compatible. Which is a VERY big deal for pro market.
Remember when Apple just "forgot" to release a pro grade desktop for years? Do you think those pros just stayed with their outdated hardware?(they didn't, they moved to Windows)
Do you think that there's a good reason for many pro software vendors to jump to Metal, when the majority of their customers are on Windows with Vulkan support?
I mentioned this on another subthread - Apple just needs to offer a cross platform API, to prove that they want pro software to be developed on Macs.
As a game dev - hardware dependence has been a fact of life for a very long time. There are too many useful extensions not included in the base profiles, and enough video cards combinatorically combined with those - that the most tractable path is to actually care about the specific device's capabilities.
The best way forward is to be as detailed as possible than to come up with a new albatross to hang around one's neck for the next 30 years. A thin driver with a fatter app stack is probably more manageable going forward than a very fat driver with a continually aging app stack, so long as appropriate care is paid to forward compatibility.
You have the benefit of abandoning your product 3-5 years after it's published, without anyone caring.
Deprecating opengl was confusing for me.
In 2011, Carmack would have gone with DirectX instead.
https://www.bit-tech.net/news/gaming/pc/carmack-directx-bett...
> The actual innovation in graphics has definitely been driven by Microsoft in the last ten years or so,' explained AMD's GPU worldwide developer relations manager, Richard Huddy. 'OpenGL has largely been tracking that, rather than coming up with new methods. The geometry shader, for example, which came in with Vista and DirectX 10, is wholly Microsoft's invention in the first place.' > > 'It is really just inertia that keeps us on OpenGL at this point,' Carmack told us. He also explained that the developer has no plans to move over to Direct3D, despite its advantages.
ARB, Long Peaks failure, not defining SDKs and leaving to ecosystem to create tools on their own, making into a rite of passage that each graphics programming student needs to create their own SDK from scratch, is anything but appealing.
If ARB/Khronos would standardize networking protocols, we would have only IP, and then each developer would create their own networking stack on top of raw IP.
They are their own GPU vendor nowadays.
Apple knows exactly what they need to do to keep the pro market on MacOSX, they are not interested in doing that at all. And that simple thing is standardization, not exclusive API. So they don't even have to support OpenGL... just not make it even harder for CAD/CAM makers to port their software/features back to MacOSX.
Lack of a good pro device for years already got a lot of pros off Macs, so companies like Autodesk have less and less value in supporting Mac. And the gap in functionality is already massive! Their vertical integration, aka platform lock-in, is impossible for companies that have majority of their customers on a different platform.(and again - Apple knows that)
You know, I'll just switch to Windows to have my designs automatically validated for code compliance... and I'll just stay with Windows for software development as well.
(I'm a software engineer studying structural engineering)
What is your quantitative evidence for saying this?
That's exactly why they should keep it. Now all those CAD programs that use older OpenGL features have to figure out how to do things that are not supported by Metal. Vulkan initially forgot about this market as well and had to add some things back in.
There is Zink to handle compatibility, but that should have come from the organizations and companied deprecating OpenGL. It should probably be standard on new platforms so they can keep OpenGL at the API level.
> To prepare for future Mac OS changes, AutoCAD 2021 for Mac uses a new graphics engine: Metal.
https://knowledge.autodesk.com/support/autocad-for-mac/learn...
They should just allow third-party OpenGL implementations. OpenGL on OSX is stuck in the past.
It would be great to see Metal die a fiery death too, and Vulkan being adopted. The current situation is just DirectX once again.
You can use ANGLE if you want, for instance?
I wouldn't recommend using OpenGL for any new software, though, it is hopelessly clunky and outdated for modern applications.