binaryen VS book

The Binaryen wasm optimizer (mentioned in the article) is always open for contributions,

https://github.com/WebAssembly/binaryen

The end of the related work section cites both wasm-smith and the Binaryen fuzzer (https://github.com/WebAssembly/binaryen/wiki/Fuzzing) and says, "They both provide a fuzzer that turns a stream of bytes into a WebAssembly module in order to test implementations. Their fuzzers always generate semantically valid test cases, but lack the targeting and tuning that Xsmith provides."

I look forward to reading more about how they do the targeting and tuning.

Binaryen or the LLVM of wasm: https://github.com/WebAssembly/binaryen

Download Binaryen

Probably https://github.com/WebAssembly/binaryen/, there were various rust bindings to it.

The final phase of our compiler is code generation. This phase takes the AST and converts it to a set of executable instructions. In our case, WebAssembly. To accomplish this, we are going to use a popular WebAssembly compiler toolchain called binaryen.

In this guide, we will be using TypeScript and NodeJS. The concepts are highly portable, so feel free to use the environment you're most comfortable with. Our only major dependency, binaryen, has a simple C API. You are welcome to skip ahead to the next section if you're using a different language.

What are the size and performance benefits of processing the Wasm payload with wasm-opt?

I would recommend looking into binaryen as it has it's own IR and can perform optimizations over it. It's also simpler than LLVM and has the option to produce binaries with debug names.

You can also use binaryen to optimize your wasm output

Like many Rust features, there is a Rust/WASM tutorial and book that was very good. I was able to follow the tutorial to get up and running with development pretty easily... though this entire ecosystem kind of has way too many moving parts. Webpack? NPM? Nodejs? Just for this? It's a bit heavyweight, but I guess like 90% of the development in the world uses stuff like this now, huh?

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