3 ms·
> OpenGL looks like it has fallen victim to design-by-committee It totally was when OpenGL was controlled by the ARB. ARB stands for "Architecture Review Board
by GuB-42 6y ago
> OpenGL looks like it has fallen victim to design-by-committee
It totally was when OpenGL was controlled by the ARB. ARB stands for "Architecture Review Board", even the name screamed "designed by committee". In the end, you couldn't do much without proprietary extensions, except using Direct3D...
After transfer the Khronos Group, it went better. Still a committee, but at least, the spec is not completely out of touch with modern hardware.
I don't know about Metal but Vulkan is not a replacement for OpenGL. It is a low level API, made so that engines like Unreal or Unity can have a lot of control and keep overhead to a minimum. However, it is absolutely terrible for small projects. It takes several pages of code to draw your first triangle.
According to the article, it looks like Metal is somewhere between OpenGL and Vulkan: lower level than OpenGL and easier to use than Vulkan. It doesn't look like Apple is doing crazy stuff with its hardware, but because they don't need to be portable, they can provide a simpler API compared to Vulkan which need to support all kinds of hardware and platforms.
I am not against Metal, however, I hate Apple for deprecating OpenGL. You used to have 3 options
1- Use an engine, and let it deal with all the rendering API stuff.
2- If you have a smallish project and want to do your own engine, use OpenGL.
3- If you are an engine developer, you make it so that it can support the best API for the system you are targeting, it can be Vulkan, Metal, DirectX 12,... and keep OpenGL for compatibility.
Now, option 1 is not portable anymore, and for option 3, you don't have a quasi-universal fallback anymore. MoltenGL/MoltenVK may be an option, but that's not ideal.
- pjmlp 6y agoOption 1 is as portable as ever, all major engines support all relevant 3D APIs, including Metal. Option 2 was never an option for most consoles (check which ones are listed at Khronos). Option 3, as per option 2 never had much gain on quasi universal API.