Vulkan support required for a pixel editor?
So I can't run this on my X220 despite having a dual-core 2.8Ghz i7 processor, since its integrated GPU is a generation just shy of having Vulkan support.
A pixel editor.
So I can't run this on my X220 despite having a dual-core 2.8Ghz i7 processor, since its integrated GPU is a generation just shy of having Vulkan support.
A pixel editor.
It’s free software. Go fork it and code up a variant for legacy hardware yourself.
It would probably be perfectly fine with even OpenGL 2.1, which would then work on every Raspberry Pi out there.
I'm not objecting to supporting hardware acceleration, modern display resolutions somewhat demand it. Just the unnecessary choice of bleeding-edge acceleration API.
With Apple’s deprecation of OpenGL on macOS, the author may not have wanted to build on top of something that’s going away.
The library I’m using used to have a gl backend, but it’s currently unsupported.
SDL - can it drive 4K displays?
OpenGL - a shattered ecosystem, with some implementations being out of date (Windows) or significantly different (ARM + OpenGL ES)
DX11 - windows only
The only real alternative would seem to be duplicating logic by implementing it for multiple backends.
------
IIUC, the author is using a library that will eventually have OpenGL supported as a backend, so I don't think your predicament is forever, assuming that you actually want to use it and aren't just complaining to complain.
What is this FUD nonsense?