cob-webber VS book

Sadly, I am too young for punchcards, however I have ported cobol to webasm ( https://github.com/wmealing/cob-webber ) and working on a gnucobo-mode for emacs ( https://github.com/wmealing/gnucobol-mode )

You willing to talk about this, because i'm stuck doing pretty much this for https://github.com/wmealing/cob-webber,

I ported gnucobol to webasm to inflict pain on future generations of programmers.

https://github.com/wmealing/cob-webber

Ncurses with vt100 emulation kinda works. But it's timing is garbage and text input is funny.

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