I've been using the wgpu-py bindings for wgpu-native but I'm concerned about the longevity and maturity of wgpu-py.
Staying on top of the wgpu-native implementation doesn't seem to be a priority for the wgpu-py maintainers.
They're also just a handful of guys working on a start up. I worry that they'll go dark and abandon their bindings.
Thoughts
Ideally I'd like to have bindings for both Dawn (C++) and wgpu-native and be able to specify which ones to use at run time.
Going my own way for bindings is a significant increase in scope however, I may be able to automate a big part of it.
Owning the bindings may ultimately be better from a performance perspective.
Learning how to do this would also be a good skill.
The Issue
I've been using the wgpu-py bindings for wgpu-native but I'm concerned about the longevity and maturity of wgpu-py. Staying on top of the wgpu-native implementation doesn't seem to be a priority for the wgpu-py maintainers. They're also just a handful of guys working on a start up. I worry that they'll go dark and abandon their bindings.
Thoughts
Tools