I kind of confuse, where to do things exactly.
I thought we should do 'everything' on WASM / Rust part?
What's the official resource to know what I can do and can't?
To elaborate, WASM is just a portable format for executables/byte code that can be interpreted or compiled and optimized; it is not an operating system.
Thanks @Michael-F-Bryan for clarifying this.
So indeed these crates give us access to manipulate DOM.
I can see the cons manipulating the DOM from Rust/WASM is a bit harder, it terms of Developer Experience. But does it have a 'significant speed improvement' as well when we're doing manipulating DOM from Rust/WASM? like the intention of WASM itself?
Things like the Component Model Proposal might be able to improve things because it'd let WebAssembly directly call into a browser's C++ code, but that proposal has been in the works for several years in different forms, so I wouldn't hold my breath.