Switching to wgpu-only backend?

[ales-tsurko]

Is there still a need for multiple backends, when wgpu uses all of them under the hood?

[Logicalshift]

Ah, yeah, the idea is definitely to get rid of the other backends. I haven't quite got around to doing that yet.

Partly, it's because the OpenGL backend is a good reference for issues with the wgpu backend, though I think that it's mostly got through the phase where that's useful now. The other issue is a weirder one: when I wrote this version of the wgpu backend, it had a lot of performance issues when running with the Vulkan backend on Windows and Linux. I think they were problems with wgpu itself and are resolved, but having the older implementation to drop back on still feels a bit reassuring.

Also I need to get FlowBetween to use the wgpu backend with the OS X frontend before I can drop Metal, it's actually not very clear how to use wgpu with an existing Swift application.

[ales-tsurko]

Ah, I see... For integrating WGPU with Swift check out this repo: https://github.com/jinleili/wgpu-in-app

I didn't look into it, but maybe you'll find it useful.