shadertoy-rs VS rust-gpu

Then, as you probably noticed, I also added my not-emulable-games-but-id-still-like-to-have-them-in-there-and-its-pretty. I added PS4, PS5, Switch games manually. Thankfully I don't buy enough of them these days that it becomes a problem to sync. As for launching, well, the TV is plugged to them. Still, they needed to be launchable (otherwise Launchbox is unhappy). What I did was fork shadertoy-rs (https://github.com/fmenozzi/shadertoy-rs). to add capabilities for randomized shaders and displaying a title. All these shaders are animated, look great in fullscreen and serve as a nice little distraction as you start up whatever console. shadertoy-rs also closes on any input, so it's easy to get back to the list. Need to also add automatically the author and the shader name for more flair. The current list of whitelisted shaders that I have on random are (beware, some of them might be a bit cpu intensive):

Sounds cool, but this requires yet another language to learn[0]. As someone who only has limited knowledge in this space, could someone tell me how comparable is the compute functionality of rust-gpu[1], where I can just write rust?

[0] https://github.com/Hugobros3/shady#language-syntax

[1] https://github.com/EmbarkStudios/rust-gpu

I don't do anything related to data science, but I feel like doing it in Rust would be nice.

You get operator overloading, so you can have ergonomic matrix operations that are typed also. Processing data on the CPU is fast, and crates like https://github.com/EmbarkStudios/rust-gpu make it very ergonomic to leverage the GPU.

I like this library for creating typed coordinate spaces for graphics programming (https://github.com/servo/euclid), I imagine something similar could be done to create refined types for matrices so you don't do matrix multiplication matrices of invalid sizes

Do you mean rust-gpu?

And https://github.com/EmbarkStudios/rust-gpu/tree/main/examples with the wgpu runner (here it runs the compute shader)

I don't know how major they are considered, but Embark Studios is doing quite a bit of Rust in the open source space, most notably (IMO) rust-gpu and kajiya

The examples in the rust-gpu repository are a good place to start

There's another project that's similar that's being used by an actual game company: https://github.com/EmbarkStudios/rust-gpu

They see specific advantages here that would outweigh that negative. It's not my space (I play games, but know next to nothing about graphics programming), but there's at least one argument in the other direction.

Could this approach work for compute shaders (GPGPU) as well? So far, I think https://github.com/EmbarkStudios/rust-gpu is the state of the art in that area, but it adds a specific Rust compiler backend for generating SPIR-V rather than leaving that up to the driver. That seems more complicated than it needs to be... but maybe it has advantages too? Thoughts?

https://github.com/embarkstudios/rust-gpu Allows you to create shaders (kernals) in Rust.

Also Embark Studios (formers DICE people) is doing a lot of work with Rust, all open source like Rust GPU https://github.com/EmbarkStudios/rust-gpu