

And now by deprecating support for these older APIs, Apple is signaling that they are reserving the right to remove them entirely in the future.Īnd unlike other OS vendors who may keep deprecated APIs around for years (if not forever) in the name of backwards compatibility, Apple has proven it has no such qualms. Instead, Apple has been pushing developers to Metal almost as soon as it became available. Apple never added support for OpenGL ES 3.1 or later on iOS, and similarly macOS doesn’t go beyond OpenGL 4.1 (Khronos is up to 4.6 now).

Instead, Apple is strongly encouraging developers to use their proprietary Metal API, which has been available for a few years now.Īpple’s lack of interest in Khronos’s Open APIs has not gone unnoticed over the years. Listed in the developer release notes for both iOS and macOS, Apple is deprecating support for what are now their legacy graphics and compute APIs: OpenGL, OpenGL ES, and OpenCL. As has long been the story at One Infinite Loop, what Apple giveth is what Apple taketh, and Apple’s latest rendition of OSes is going to be no exception.
