cumulus VS rust-gpu

The Bridge Hub will eventually allow communication and interaction between Polkadot and other networks such as Kusama and Ethereum. For technical details including the chain spec, see https://github.com/paritytech/cumulus/releases/tag/parachains-bridge-hub-polkadot-v9382

For more details on the Kusama Bridge Hub, see https://github.com/paritytech/cumulus/releases/tag/parachains-bridge-hub-kusama-v9360

Core development XCP and XCMP issues on cumulus https://github.com/paritytech/cumulus/issues

Note that this version of Statemint has teleports and permissionless asset creation DISABLED. These features will be enabled in a future update. https://github.com/paritytech/cumulus/releases/tag/statemint-v6.0.1

Great question. While the back-bone of Polkadot is Substrate, and using Substrate comes with the benefit of having a direct approach in becoming a parachain (e.g. using the Cumulus library - Parachain module) non Substrate-based chains can be deployed onto Polkadot.

Statemine V3 was released. Please update if you are running a Statemine node. https://github.com/paritytech/cumulus/releases/tag/statemine_v3

Cumulus code: https://github.com/paritytech/cumulus/.

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