Azul3D VS wgpu-native

Interesting work Nikki, I've definitely considered going down this path once or twice with Azul3D in years past, cool to see you've gone much further with it than I ever did.

Having a nice API to programmatically work with audio, though, I think is also super important. One thing I did right with a (now-defunct) engine I worked on a long time ago, Azul3D, was put together an truly nice audio library for working with samples in various formats akin to Go's image standard library (if you've ever used that, you'll know why having a common interface to manipulation is super nice.)

The Mach engine project has prebuilt Dawn libraries and also a simplified build-from-source process using the Zig build system, see:

https://machengine.org/pkg/mach-gpu-dawn/

It's also possible to use wgpu-native in C/C++ projects as prebuilt library, see:

https://github.com/gfx-rs/wgpu-native

It is based on the wgpu-native implementation (Firefox backend) but I plan on adding a receipe for using it with Dawn (Chrome backend) as well.

go-webgpu provides binding for wgpu-native (a safe and portable GPU abstraction in Rust, implementing WebGPU API).

Rust, C++

When you look at graphics APIs in Rust practically everything is pointing towards, and telling you to use, wgpu, which abstracts over Vulkan, Metal, DX11/12, GLES and WebGPU and is based on, drumroll, WebGPU. Hardly surprising as it's the backend firefox is going to use. And yes it has a C API, too.

Probably the easiest option would be to target wgpu-native prebuilt binaries but these don't have iOS/Android (unsure if wgpu-native supports iOS/Android at all)

WGPU is the underlying implementation for WebGPU in Firefox and it has C bindings: https://github.com/gfx-rs/wgpu-native.git.