> Unlike ours, the manufacturer’s M1 drivers are unfortunately not conformant for any standard graphics API, whether Vulkan or OpenGL or OpenGL ES. That means t

> Unlike ours, the manufacturer’s M1 drivers are unfortunately not conformant for any standard graphics API, whether Vulkan or OpenGL or OpenGL ES. That means that there is no guarantee that applications using the standards will work on your M1/M2 (if you’re not running Linux). This isn’t just a theoretical issue. Consider Vulkan. The third-party MoltenVK layers a subset of Vulkan on top of the proprietary drivers. However, those drivers lack key functionality, breaking valid Vulkan applications. That hinders developers and users alike, if they haven’t yet switched their M1/M2 computers to Linux. This becomes very obvious to anyone who has to debug now-deprecated OpenGL apps in macOS, because the abstraction layers do not actually expose OpenGL state in ways that old Apple OpenGL debuggers can read. Which means unless you still have old Macs, with old versions of macOS installed where OpenGL is not Metal under the hood (I can't even remember the last version where that was true) then it's literally not possible to debug OpenGL on macOS anymore using stock debuggers. Your debugger and or app will just crash.