3 ms·

It’s annoying that Apple already has an implementation of OpenGL on Metal, but they don’t share the source and they also put up a lot of deprecation warning noi

by pavlov 4y ago

It’s annoying that Apple already has an implementation of OpenGL on Metal, but they don’t share the source and they also put up a lot of deprecation warning noise to discourage you from using it.

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 ago
  Yes, that’s because it’s deprecated and that’s why you get all these warnings.
  - Rhedox 4y ago
    It's not just about warnings, Apple only supports OpenGL 4.1 which was released in 2011.
    - waynecochran 4y ago
      OpenGL 4 is not the “really old stuff”
      - vetinari 4y ago
        Between 4.1 and 4.6, it changed a lot. Apple never supported extensions for AZDO, for example.
      - Rhedox 4y ago
        It's missing features that D3D11 had in 2009. Compute shaders in particular are a huge feature that GL4.1 doesn't have.
- pavlov 4y ago
  It’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 ago
  No… 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 ago
    4.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 ago
      So what? There are plenty of applications that just render graphics and don’t need compute shaders.
    - waynecochran 4y ago
      What I call "really old stuff" uses glBegin() and glEnd()
- flohofwoe 4y ago
  It's GL 4.1 Core Profile (which was specced in 2010), in "OpenGL years" that's still pretty new ;)
  - bl0b 4y ago
    Yeah.. no compute shaders though, among other things
w0mbat 4y ago
Yes the nagging is annoying. I finally added this to my prefix header. #define GL_SILENCE_DEPRECATION 1
ranger_danger 4y ago
VSync under OpenGL is also currently broken on OSX. It broke in 12.0, then was fixed in 12.1, and is now broken again in 13.0. https://github.com/glfw/glfw/issues/1990 https://github.com/glfw/glfw/issues/1990
deleted 4y ago
[deleted]

by pavlov 4y ago

It’s annoying that Apple already has an implementation of OpenGL on Metal, but they don’t share the source and they also put up a lot of deprecation warning noise to discourage you from using it.

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 ago
Yes, that’s because it’s deprecated and that’s why you get all these warnings.
- Rhedox 4y ago
  It's not just about warnings, Apple only supports OpenGL 4.1 which was released in 2011.
  - waynecochran 4y ago
    OpenGL 4 is not the “really old stuff”
    - vetinari 4y ago
      Between 4.1 and 4.6, it changed a lot. Apple never supported extensions for AZDO, for example.
    - Rhedox 4y ago
      It's missing features that D3D11 had in 2009. Compute shaders in particular are a huge feature that GL4.1 doesn't have.
pavlov 4y ago
It’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 ago
No… 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 ago
  4.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 ago
    So what? There are plenty of applications that just render graphics and don’t need compute shaders.
  - waynecochran 4y ago
    What I call "really old stuff" uses glBegin() and glEnd()
flohofwoe 4y ago
It's GL 4.1 Core Profile (which was specced in 2010), in "OpenGL years" that's still pretty new ;)
- bl0b 4y ago
  Yeah.. no compute shaders though, among other things

w0mbat 4y ago

Yes the nagging is annoying. I finally added this to my prefix header. #define GL_SILENCE_DEPRECATION 1

ranger_danger 4y ago

VSync under OpenGL is also currently broken on OSX. It broke in 12.0, then was fixed in 12.1, and is now broken again in 13.0. https://github.com/glfw/glfw/issues/1990 https://github.com/glfw/glfw/issues/1990

deleted 4y ago

[deleted]