wgpu-native VS bgfx

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.

Sort of, I'd recommend a modern higher level API. I'm not sure what the current recommended ones are (probably bgfx), but assuming the wrapper is "low level enough", then the concepts you learn are still going to apply.

https://github.com/bkaradzic/bgfx for just that FOSS intermediate rendering library (includes Minecraft)

BGFX: Pretty mature and easy to use with many backends.

bgfx. I have not used it, but I have heard good things about it.

There's kind of a lack of this for C++ in 3D, I think it's often due to the necessity of a secondary scripting language in game engines with C++, which isn't necessarily needed in Java or C#. SFML is like that (but also 2D), Godot is similar (but more geared towards 2D). Ogre3D is an actual engine like I mentioned earlier, not sure how easy it is to use. Cocos2d is higher level, but is also 2D only. I'm not fond of SDL, it feels like a windowing library with slow old school immediate mode stuff attached, so it ends up not being good at the rest of the tacked on things. SDL is popular as a windowing library, and it's why you see it used everywhere (but the most notable uses of it aren't using their drawing capabilities), I often see bgfx thrown around, and for you it might be a good choice, though I have no experience with it.

Another route could be using an abstraction over Vulkan (faster, more efficient, more difficult): bgfx, dawn, magma, or wgpu (Rust).

now, java is actually quite a performant language and even if its not most of the performance bugs in mc are due to it being single threaded, inefficient chunk generation and optimizing, and it built ontop of opengl WHICH isn't much of a performance hit but its still ehh idk it doesn't matter that much (NOW SWITCHING THE GAME TO AN ENTIRELY DIFFERENT GRAPHICS API WOULD SUCK ASS TO DO (and vulkan is quite verbose :))) (AND also bgfx would probably be better due to it being an abstraction layer ontop of all the graphics apis so minecraft could target many depending on your platform (and also bedrock used to (or still does i dont know) use bgfx before they switched to just two (IF IM READING MC WIKI RIGHT BECAUSE IM NOT ENTIRELY SURE IF THEY USE BGFX STILL ?? SO THEY COULD STILL BE TARGETING MULTIPLE YET THEY JUST WROTE THEIR NEW SHIT BAD IDK))