3 ms·
Am I remembering correctly in that it doesn’t support modern OpenGL features, just the really old stuff that the old implementation did?
by saagarjha 4y ago
Am I remembering correctly in that it doesn’t support modern OpenGL features, just the really old stuff that the old implementation did?
- tinus_hn 4y agoYes, that’s because it’s deprecated and that’s why you get all these warnings.
- Rhedox 4y agoIt's not just about warnings, Apple only supports OpenGL 4.1 which was released in 2011.
- waynecochran 4y agoOpenGL 4 is not the “really old stuff”
- pavlov 4y agoIt’s fine for practically all existing applications. There’s no real reason why Apple should deprecate it instead of opening the source and letting pro apps that rely on OpenGL continue to use this wrapper. The community could implement newer API features, and then everyone just links and includes the version of OpenGL on Metal that they want. Wrappers are used by the majority of apps anyway, for example WebGL. Apple doesn’t get to say: “We want your JavaScript apps to use our API instead, and we’ll make the development experience subpar if you’re using WebGL.” — they shouldn’t have that kind of power over C apps either.
- waynecochran 4y agoNo… I used to do a lot of OpenGL programming and AppKit supported a fairly modern version… Apple deprecated it and it has really sucked for me.
- Rhedox 4y ago4.1 is not a fairly modern version. That was released in 2011 and doesn't even have compute shaders which D3D11 had in 2009.
- pavlov 4y agoSo what? There are plenty of applications that just render graphics and don’t need compute shaders.
- waynecochran 4y agoWhat I call "really old stuff" uses glBegin() and glEnd()
- flohofwoe 4y agoIt's GL 4.1 Core Profile (which was specced in 2010), in "OpenGL years" that's still pretty new ;)
- bl0b 4y agoYeah.. no compute shaders though, among other things