Comment by api
9 hours ago
These days you could just ask a bot to port your stuff from OpenGL to a newer API.
Backward compatibility is less of an issue when fixing legacy stuff takes $25 in tokens.
9 hours ago
These days you could just ask a bot to port your stuff from OpenGL to a newer API.
Backward compatibility is less of an issue when fixing legacy stuff takes $25 in tokens.
Unfortunately there is no universally supported newer API thanks to Apple.
There's some libraries like wgpu that can fill this gap in practice
Minecraft has been moving to Vulkan and using MoltenVK to run the same backend on Mac.
In that case maybe the answer is $200 in tokens to make a metal OpenGL shim and then share it to the community on GitHub.
Given the comparable performance of OpenGL and Metal on the same hardware I was under the impression that is how Apple had been implementing OpenGL for quite a while.
2 replies →
ANGLE already does that: https://chromium.googlesource.com/angle/angle
Isn't https://github.com/google/angle just that?
Edit: I guess no, Angle is OpenGL ES. My bad.
1 reply →
Metal is universally supported among Apple's product lines.
Just as useful as DirectX being universally supported in Microsoft's product lines.
The point of OpenGL was to have an API universally supported everywhere
5 replies →
Everything is universally supported in a small enough universe.
Shouldn't Apple be the one spending the $25 to deliver a product that works?
I can port _my_ stuff away from OpenGL, but can't port 3rd party or legacy software that I use.
"Why have X when Y costs $N in tokens" is becoming a tired thought-terminating cliche.
It shouldn't be user's responsibility to have to get their binaries to work at all costs.
How about they spend $25 in tokens to fix what they broke?
Why, yes, of course, have all the devs in the world spend $25 and tons of time each, because Apple doesn't care about devs nor users.
/s