zink

It's better to let something like Zink handle OpenGL rather than try to provide an OpenGL interface.

The zink.shield is a python decorator that you can fit nicely in your existing RAG/LLM apps.

It's not such an immediately cool thing as radv or zink, but it's still useful.

In addition, you can offload OpenGL compatibility to Zink (again leaning into Vulkan).

The only two I found really interesting was zink and desktop factory.

The long-term future for OpenGL is to be implemented on top of Vulkan (specifically the Mesa Zink driver that the blog post author is the main developer of).

Once I had to use a Mesa3D build for Windows and use the zink driver to render OpenGL to Vulkan, otherwise it would use Windows' software renderer.

The hardest part was to provide a couple of required extensions and massaging Zink to use our Vulkan device with our extensions and also stub out its memory allocator for ours.

This is nice, but what I really would like is for someone to make the Zink + MoltenVK/KosmicKrisp combo so that we can have OpenGL 4.1+ support on macOS.

Not just that, we actually ship Zink with our Vulkan based game because for absolutely insane reasons many years ago the decision was made to expose a GL context to plugins for graphics work.

They didn't need to strictly speaking back zink either (OpenGL on Vulkan), but they decided to and it gives them a long term ability to have OpenGL even if native drivers will be gone, as well as an upside of bringing up OpenGL on any Vulkan available target out of the box.

Zink clarifies he calls himself a “conservative” over calling himself a “Republican.” He doesn’t like Trump’s inflammatory rhetoric.

Oh, and making sure we get to get dibs on loading opengl32.dll/libgl.so that translates into Zink.

Mike is an absolute legend for all of his work on Zink.

Zink makes sense because it closes a unique gap (supporting older games if OpenGL support sunsets) in their platform, not just for its own sake.