News for hackers. Stuff that matters.
Re:Deprecation of OpenGL and OpenCL by fooster on Monday June 04, 2018 @08:45PM (#17234039)
> for example, it will randomly recompile shaders behind your back while you are trying to have a smooth frame rate.

What? I've written commercial games with opengl on osx/ios and my experience doesn't show that at all.

Re:Deprecation of OpenGL and OpenCL by jblow on Monday June 04, 2018 @08:51PM (#17234077)
Maybe the games were not very complex? Professional game programmers building games with lots of shaders are very familiar with what I am talking about. See for example this thread:

https://www.opengl.org/discussion_boards/showthread.php/1998...

Re:Deprecation of OpenGL and OpenCL by exDM69 on Tuesday June 05, 2018 @04:20AM (#17235834)
> What? I've written commercial games with opengl on osx/ios and my experience doesn't show that at all.

State-based recompilation is a known issue in many GL drivers, particularly on mobile. E.g. changing blending settings may cause shaders to get recompiled. This can take up to a second.

Some engines work around this by doing a dummy draw to an offscreen surface with all pipeline configurations that they use at init time. This (usually) guarantees that all the shaders are pre-compiled.

Re:Deprecation of OpenGL and OpenCL by fulafel on Tuesday June 05, 2018 @12:31AM (#17235010)
Also, you can handle caching of compiled shaders yourself now (glProgramBinary).
Re:Deprecation of OpenGL and OpenCL by 0xcde4c3db on Tuesday June 05, 2018 @09:34AM (#17237410)
I think the recompilations being talked about here are shaders generated by the OpenGL implementation behind your back. That is, your program never sees them as shader or program objects because they implement some permutation of blend mode, depth test, culling type, etc..