upterm VS book

The reason you don’t see a feature like blocks (with the exception of Upterm) in most other terminals is because the terminal has no concept of what program is running, or really of anything that’s happening within the shell. At a high level, a terminal reads and writes bytes from a pseudoterminal to interact with the shell. This technology is very antiquated--the shell essentially thinks it is interacting with a physical teletype terminal even though they haven’t been used in practice in over 30 years!

Suprised that no one has mentioned this, but upterm seems to be exactly what you're describing--a terminal emulator that shows a drop-down list of suggestions with explanations. Sadly, only a few commands are supported, and it's no longer being worked on.

Currently haven't gone as far as making some kind of dedicated shell component though. I find it important that normal shells can work fine with in Extraterm. There was a project from a few years back which also mashed GUI/emulator together with the shell side, Upterm. SSH and containers tend to be the natural enemy of having your own shell though.

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