Or we'd just wait for the inevitable opengl->vulkan and opengl->metal translator layers to mature like Angle for opengl->direct3d. It's completely unrealistic to expect that all opengl programs, with often more than one or two decades of investment go and drop that investment and start porting to the hype du jour.

Angle is the best bet: https://github.com/google/angle

And in the meantime, we do our best on macOS, but it's not our priority platform, and it will never be. Much like macOS isn't Apple's priority platform.

Al Martinsen wrote:OpenGL is going to be deprecated in the future (if not already: the latest stable release is FROM 2017)

Say who? (besides maybe Apple, conveniently)
Khronos clearly said OpenGL will keep evolving alongside Vulkan. Of course the pace slowed down, but 4.6 did adopt some interesting things from the Vulkan development.
And by that logic, Direct3D 12 is about to be deprecated too, because aside from a raytracing extension tacked on for nVidia, nothing was added to in in the last 2 years either.

Al Martinsen wrote:Apple deprecated OpenGL because they are focusign on their own low level GPU acceleration (Metal), and the reason is obvious: about a 40% performance increase.

Which isn't exactly hard when your OpenGL performance tends to look like this:
https://www.phoronix.com/scan.php?page= ... ming&num=2
Then Vulkan (via MoltenVK) just barely gets you back to where OpenGL already was on Windows and Linux:
https://www.phoronix.com/scan.php?page= ... lkan&num=2

Of course it's much more convenient for Apple to only offer a proprietary low-level API. You can declare any behavior as intended, and offering abstractions that perform well is not your issue anymore, easy.
But the necessity for abstraction doesn't just go away because you decide to throw it out of the driver, nobody is going to add hundreds of low-level calls in their own code over and over again.

And don't omit that OpenGL 4.2 - 4.5 did quite a bit to reduce CPU overhead, but Apple decided to let it bit-rot at 4.1 and not even fix crucial bugs. That of course makes it easy to claim your shiny new API is waaaaay faster than the old solution.
Yes Vulkan/Metal/Direct3D12 can feed the GPU faster when the CPU gets the bottleneck, but by far not every application/game has that issue to begin with.

i can't draw with krita on my 3k macbook pro unless i use bootcamp (windows), this is really infuriating. Hopefully i have a grounded computer in my parent's house

Why are you asking that question in this thread? Isn't the content of the thread enough of an answer?