angle

Anyone that intends to run OpenGL applications in Win32 sandbox, UWP sandbox or just use store apps. The OpenGL 1.1 ICD driver model that OEMs take advantage of to deliver more modern drivers isn't supported in those scenarios, and most likely is going away with either Windows 10X or some future version of it. https://devblogs.microsoft.com/directx/in-the-works-opencl-a... Microsoft also had a version of this back when Windows 8 got released, https://github.com/microsoft/angle

Android got optional Vulkan support on version 7, yes. And by being optional, meant most OEMs cared as much as the optional updates. Hence why on Android 10, Google took a set of actions, made Vulkan mandatory, started the path to have OpenGL ES on top of Vulkan and introduced GPGPU driver updates via the Play Store, as means to force OEMs to actually care about Vulkan. Just like many devices still don't ship with OpenGL ES 3.x, because it is optional as well. There a reason why I mentioned Win32 and UWP sandboxing and not just UWP. Yes the pure UWP model although quite nice to program for (for me it is what .NET 1.0 should have been all along) failed to gather the mass adoption that Microsoft hoped for, and that is why since two years they have changed course to merge both worlds, now officially known as Project Reunion. As a matter of f

Then you will only target Linux. OpenGL and Vulkan only happen to work on Windows via the ICD driver model introduced in OpenGL 1.1, which Microsoft hasn't yet bothered to remove. Instead they aren't supporting it on UWP and Win32 sandbox model, which only allow DirectX. Microsoft's way forward is also to build OpenGL wrappers on top of DirectX like ANGLE. https://github.com/microsoft/angle/wiki https://devblogs.microsoft.com/directx/in-the-works-opencl-a... And then there are the game consoles. Khronos has just messed up providing SDKs that are at the same productivity level as commercial APIs.

MoltenGL proprietary and not the only implementation of the GL library on top of modern APIs. There's also ANGLE. It worked pretty OK-ish in my project running OpenGL game on Windows Phone 8. I was using Microsoft's fork [2]. Another alternative is GLOVE [3], which is a software OpenGL on top of Vulkan. Another interesting project is WebGPU [4] which targets to provide Vulkan-like APIs across various platforms in browsers. As it's offshoot which is not quite related is GFX-rs, which became a cross-platform Rust library providing low level graphics API (HAL layer). looking forward seeing ANGLE getting Metal backend, which been just a promise so far. [1] https://github.com/google/angle [2] https://github.com/Microsoft/angle [3] https://think-silicon.com/products/software/glove/ [4] https://en.wikipedia.org/wiki/WebGPU [5] https://github.com

> GLSL is used for multimedia apps, user interfaces (Qt at least uses it quite a bit), 3D authoring apps. ISF (Interactive Shader Format https://www.interactiveshaderformat.com/spec), fairly used in all the software chain around audio-visual installations, is based on GLSL. It's used on android, on embedded devices, etc etc... Google and Samsung are developing HLSL compiler for Vulkan, because a large majority of game studios don't want to bother with Vulkan on Android if they cannot port their shaders. There are plenty of HLSL compiler status talks at the Khronos web site and YouTube channel. > > And since Windows and macOS/iOS don’t support Vulkan, > now this is just FUD. you can entirely write vulkan code and have it run on windows and apple platforms. On the contrary, this is quite true. Apple does not support Vulkan, you need VulkanM

Only on desktop. In case you missed the news, only DirectX is supported on UWP and store apps. To the point that Microsoft has their own port of Angle. https://docs.microsoft.com/en-us/windows/uwp/gaming/compare-... https://github.com/Microsoft/angle So unless they change their mind, say goodbye to ICD drivers on Windows as well.