The size of the ecosystem that use it is so large and across all platform, that completely removing the ability to have an OpenGL context would be extremely costly, even for Apple (Who would decide to cut WebGL on MacOS?). I think that OpenGL will be available for the foreseeable future on all platform. Sadly, I'm not familiar enough with either GLFW or fyne to pick out the exact code parts.Īt the end of the day, the end-developer of fyne should be able to decide what to use via vulkan/ opengl go build tags, or something along the line.Īnd those who want to build for macOS can then, in the future where OpenGL does not run on macOS anymore, use the vulkan build tag and link their app to MoltenVK. So those parts need a Vulkan equivalent in fyne. I saw some Context namings in fyne code (and I assume it stems from the naming convention of GLFW). OpenGL (ES) is called Context in GLFW, from what I can see in the introduction. there needs to be Vulkan code (hopefully this is fully realizable via GLFW).next to the existing OpenGL code (which should work for other OS than macOS for the foreseeable future),.MoltenVK - free (as in beer) and open-source

Therefore, end-developers will have to use MoltenGL (which requires a commercial license).

MoltenVK will not help, as fyne uses OpenGL.

Sorry if it was confusing, I learned more/better about this issue over the course of our discussion.Īll code should still be working on macOS - for now, at least.įyne will not work anymore, when Apple decides to abolish OpenGL on macOS (can by any day, or maybe only in 2 or 5 years).

Mac os opengl driver