18 ms·
Neither Apple nor Microsoft want any usable multiplatform graphics API. For this reason, none of them delivers such a thing. If you want a multiplatform graphi
by Const-me 3y ago
Neither Apple nor Microsoft want any usable multiplatform graphics API. For this reason, none of them delivers such a thing.
If you want a multiplatform graphics API, you should use a library which implements such API on top of these native OS-specific APIs.
I have good experience with that one: http://diligentgraphics.com/diligent-engine/ http://diligentgraphics.com/diligent-engine/ I’ve used it couple times on Windows with D3D12 backend, and on Linux with GLES 3.1 backend.
- ClumsyPilot 3y ago> If you want a multiplatform graphics API, you should use a library which implements such API on top of these native OS-specific APIs. Typical software approach- instead of fixing the fundamental problem, just put a plaster on top. That’s how we deal with everything. Thats why our industry can’t be trusted.
- Const-me 3y agoHow would you fix the fundamental problem? It’s technically possible to force these two companies to implement a shared API, but hard to do, and “Vulkan API Support Act of 2024” sounds a bit weird, IMO.
- ClumsyPilot 3y agoWe do it in other industries all the time, petroleum fuels content is regulated that way for compatibility. We have a ‘electrical plugs act’, ‘fire hydrant act’, ‘railway standards act’, ‘air traffic control act’, ‘water mains act’, etc.
- Const-me 3y agoI think the #1 reason for these regulations wasn’t compatibility, it was safety. People die in fires, railway accidents, aviation disasters, and from waterborne infections.
- ClumsyPilot 3y agoWell safety argument is now relevant, as software is Joe , controlling all those things