The deprecation of OpenGL from macOS

A place to discuss things that aren't specific to any one creator or game.
Forum rules
Ren'Py specific questions should be posted in the Ren'Py Questions and Annoucements forum, not here.
Post Reply
User avatar
Miko-Class Veteran
Posts: 929
Joined: Sun Jun 27, 2010 12:54 pm
Organization: MysteryCorgi
Tumblr: MysteryCorgi
Deviantart: MysteryCorgi
Soundcloud: MysteryCorgi
itch: MysteryCorgi
Location: USA

The deprecation of OpenGL from macOS

#1 Post by Morhighan » Mon Jun 04, 2018 9:11 pm

OpenGL is deprecated in 10.14 Mojave, according to the latest announcement for macOS.


Developers still be able to use OGL in macOS, but this makes it official that Apple will no longer be updating or adding to it. I know that many games and apps use OpenGL and so developers will be having to adapt to using the new Metal and Metal Performance Shaders. In my opinion, developing for the Mac now requires an attitude of evolve or perish. I suspect for many indie developers, Mac support will no longer be worthwhile, especially when it is so difficult and unfriendly to unexperienced users.

I would be interested to see what you all have to contribute on this matter, as fellow developers.

User avatar
Lemma-Class Veteran
Posts: 2850
Joined: Mon Dec 14, 2015 5:05 am
Location: Your monitor

Re: The deprecation of OpenGL from macOS

#2 Post by Imperf3kt » Tue Jun 05, 2018 2:57 am

I doubt this affects Ren'Py, as Ren'Py uses OpenGLES2.0, which is not the same as OpenGL
Warning: May contain trace amounts of gratuitous plot.
pro·gram·mer (noun) An organism capable of converting caffeine into code.


User avatar
Posts: 142
Joined: Sat Jan 16, 2016 6:01 pm
Projects: Tenkeiteki Tokyo

Re: The deprecation of OpenGL from macOS

#3 Post by Fuseblower » Tue Jun 05, 2018 5:10 am

I think most developers won't notice much of it since they'll be using a cross-platform development tool (like Renpy). Of course, Apple does everything in its power to make it hard to cross develop for its own platform. That hasn't changed. But we still have HTML 5 :lol:

Anyway, graphics functions should always be wrapped in a class or some other kind of interface so that any change or addition in the underlying graphics hardware or API only results in a need to change that wrapper code and nothing else.

In the old days we had to write for different stuff like VGA, CGA, EGA, Hercules, etc. And to have any kind of hardware acceleration (if there was any at all) we had to write for specific graphic cards (like writing code for a Matrox Millenium, for example).

Worse : the graphic assets themselves had to be made specifically for each of these graphic adapters because the resolutions and the colors were wildly different. Even on home computers like the Atari ST there was the problem that some people used a black and white monitor giving 640x400 (in black and white, of course) but those people couldn't use the glorious 16 color 320x200, and vice versa because the color monitors couldn't do the high resolution of 640x400. Many had two monitors because of this (the color SC1224 and the monochrome SM124 or SM125). The Commodore Amiga didn't have this problem and had a higher resolution (by cutting the speed of the CPU in half!).

But enough of those old horror stories. My beef with Apple is not that they do this thing, Microsoft isn't a stranger to such tactics (even when it comes to those rare APIs they developed themselves like ODBC). My beef with Apple is that they're unfriendly to developers in general. You don't see Microsoft demanding money from developers for the "privilege" to use their OS. I'm surprised Apple still has a market share at all :lol:

Post Reply

Who is online

Users browsing this forum: No registered users