wgpu-rs

You should check out the Rust WebGPU implementation https://github.com/gfx-rs/wgpu-rs

We let wgpu https://github.com/gfx-rs/wgpu-rs handle our graphics backend abstraction, so our OpenGL support will come whenever they implement and release it. Currently, it seems to be a WIP.

I think Rust and Haskell, due to their irrelevance in industry and general "nerdiness", attract a certain type of hacker. Specifically I've noticed that there are some libraries for both languages that are just so good that they make you never want to use anything else. One example in Haskell is Megaparsec [0], by far the best point in the parser framework design-space I'm aware of. An example in Rust is wgpu-rs, which maybe isn't "all the way there" yet but is already turning into a very ergonomic low-level rendering API. Although I haven't used them, I think piet-gpu and pathfinder may be in this category also. I don't have a link handy but I remember seeing a tweet from the developer of Pathfinder where he was reverse-engineering MacOS's idiosyncratic font rendering so he could generate identical-looking output as the native renderer.

There are lots of options for graphics in Rust, so it's really just a choice of which graphics API you'd like to use or learn more about. (full disclosure: I contribute to some of these crates) For example, there is an implementation of WebGPU (https://github.com/gfx-rs/wgpu-rs) that can run both inside and outside of the browser that has been growing in popularity lately. There are also bindings for Vulkan (ash, erupt), D3D12 (d3d12-rs), Metal (metal-rs), cross-platform abstractions at various levels (gfx-hal, wgpu), OpenGL (glow, glium), etc. It's also possible to simply render graphics to an image (a pretty common approach for Raytracing in One Weekend) or blit pixels onto a window surface.

WebGPU is going to be dope. It goes beyond the web. https://github.com/gfx-rs/wgpu-rs

Rust has its own stuff going on: https://github.com/gfx-rs/wgpu-rs

Check out wgpu (https://github.com/gfx-rs/wgpu-rs) the Rust implementation of the WebGPU standard. WebGPU is a nice API, Rust is amazing too. It's the stack of the near future. You can use it on the desktop. WebGPU a fast API on top of the underlying platforms. And it supports spirv, fuck glsl or hlsl. There's also a dedicated wgpu channel on matrix if you want to join. https://matrix.to/#/%23wgpu:matrix.org

Rust. WebGPU (the WGPU implementation is nice https://github.com/gfx-rs/wgpu-rs). Also ECS.

It's also cargo and the way the build system works. Build scripts in Rust are written in Rust, not some ad-hoc declarative build language. This is a really good decision because you can do insane shit in your build scripts. Also macros, you can generate say bindings relatively easily. I've been doing some cross-platform GPU stuff lately and Rust makes so much of this a breeze. I can't imagine combining C++ projects this easily. I'm really bullish on wgpu (https://github.com/gfx-rs/wgpu-rs). It's the Rust implementation of the WebGPU standard. It goes beyond the web though, it's a really nice GPGPU API to work with and will be a popular API in the next decade.

There is another translation layer called wgpu (https://github.com/gfx-rs/wgpu) being developed as well. It's written in Rust and has bindings for C, Rust (https://github.com/gfx-rs/wgpu-rs), and some initial support for other languages (Python, Julia, Scopes, etc.). Dawn and wgpu have also been collaborating to create a common set of WebGPU headers. The WIP headers are located at https://github.com/webgpu-native/webgpu-headers if you're interested in contributing or following.