wasm-bindgen-rayon VS book

This crate may be of interest to you

The problem is rayon. There an experimental implementation for the web here, but it has to be explicitly used by the code, as far as I know.

Thanks! Agreed--this project was possible thanks to the excellent wasm-bindgen-rayon crate which was recently released.

I would recommend reading RReverser's articles on multithreading online. We used https://github.com/GoogleChromeLabs/wasm-bindgen-rayon and ended up forking it due to chromium issues with nested web workers.

you can use rayon with your wasm-project with this crate now. https://github.com/GoogleChromeLabs/wasm-bindgen-rayon

For more information, you can refer to the Rust and WebAssembly.

As a starting point for Rust in general, you should read the book. And if you got some grasp of Rust, you should take a look at the book about Rust and Wasm.

I am following the Rust Wasm book. I have the following struct.

https://rustwasm.github.io/docs/book goes over how to compile to WASM and rendering to a canvas.

Rust 🦀 and WebAssembly 🕸 (英語)

I'm a little confused about how Rust fits into your UI-for-a-Python-API thing. Web UIs are typically written in Javascript or something that compiles to Javascript. Compiling Rust to Javascript is a not a common use of Rust at this time. The typical use of Rust in a web application would be the part that runs on the server (the "backend"), not the part that runs in the web browser (the "UI"). While you can write web UIs in Rust, this is a thing better learned after learning the normal way to do it, in Javascript.

AFAIK unwinding in WASM is not a thing: https://github.com/rustwasm/book/issues/76

Honorable mentions: 1. Easy Rust for a general overview of the commonly used features 2. Rust/WASM for developing WASM apps in Rust