glium VS wgpu

Which is blocked, waiting for glium to update: https://github.com/glium/glium/pull/2036

https://crates.io/crates/glium (8 months ago - 925 kB)

Hi rustaceans! I glued this prototype together with vtkio and glium. There are more features that are unsupported than supported at this point, but the code is here if you want to check it out: https://github.com/JeffIrwin/skillet

Should i learn glium (https://crates.io/crates/glium)? i have some experience in opengl (C++) and i would like to use the opengl functionality in the Rust ecosystem.

I can recommend https://github.com/glium/glium as a good, safe abstraction. There was a time when I wanted to learn shaders and write complex pipelines with several stages, this library allowed me to learn about the important objects and their responsibilities without having to program the very verbose chunks of code to initialize. I learned the following:

Glium is a Rust-y OpenGL wrapper, and its repository contains a discussion that should give you an idea whether this is what you want to use, as well as some tutorial.

If you don't know C++, don't let that deter you because if you can read Rust, you can read the C++ the author writes in the book. To interact with OpenGL I used glium; translating the C++ code to Rust/glium can be tricky though. The Rust equivalent to the linear algebra library the author uses (GLM) is nalgebra_glm.

Glium and ash provide low level access to different common graphics api's. I'm sure there's a good directx-11/12 bindings as well but I'm unfamiliar with what people use.

I was following the glium tutorials and I thought that I could play around with the code and move most of the logic over into a struct similar to what is done in this wgpu tutorial. However when I try to do that I get an issue saying that a move occurred because my struct didn't implement the copy trait, although neither did the tutorial on wgpu, so I am a bit confused as to why it works in the wgpu code and not in my code.

glium: https://github.com/glium/glium/tree/master/book wgpu: https://sotrh.github.io/learn-wgpu/

That's a known problem, and it's now getting attention after my previous post.

I am trying to use the imgui crate (along with imgui-winit-support and imgui-wgpu) with wgpu. I have followed the imgui-wgpu example and have gotten everything to work on the native version of the project.

There is an example of wgpu and compute, but it doesn't look easy: https://github.com/gfx-rs/wgpu/tree/master/wgpu/examples/hello-compute

I see some weirdness in the wgpu crate, it seems like for some reason it thinks every line of most files changed between 0.15.0 and 0.15.1 (eg) when in reality there were only a dozen or so commits, none of which even touched that file (github diff for the same range).

wgpu (https://github.com/gfx-rs/wgpu) low-level graphics API

wgpu needs to iterate on storage locks, that has been known but wasn't prioritized yet. Connor wanted to fix this badly, and hopefully will find time to do so. Most of the effort was spent on chasing WebGPU spec, and good news is - it's pretty much final, with Chrome releasing its implementation any month now (and Firefox/Safari hopefully following). So naturally we should expect the focus to slowly shift into performance in this year.

are you confusing it with WebGL?

we're talking about https://github.com/gfx-rs/wgpu which has Vulkan, Metal and DX12 backends

Compare the basic examples to draw a simple shape like a triangle in wgpu (https://github.com/gfx-rs/wgpu/blob/master/wgpu/examples/hello-triangle/main.rs), and in macroquad (https://github.com/not-fl3/macroquad/blob/master/examples/basic_shapes.rs).

https://github.com/gfx-rs/wgpu is as bare bones as it gets