Open emschwartz opened 5 years ago
I am interested in taking this issue, but I must admit that I have no experience with yew
or percy
. I would like to improve error handling throughout the existing crates before I commit to this though.
Do you think using Javascript would be more appropriate once the Rust API has stabilized, so more experienced designers could contribute to this project? For specs, should it mirror the CLI?
I don't feel that strongly about whether it should use a rust or JS framework. I think a (graphic) designer could work on the HTML and CSS independent of which category of frameworks we go with.
I'd want it to leverage all of the underlying API endpoints and enable you to:
As a huge fan of server-side Rust who also likes doing frontend stuff, my personal preference for this sort of thing is TypeScript
@tarcieri have you tried yew or percy? Just curious what the experience of using those is like. The idea of isomorphic web apps using Rust and wasm seems pretty awesome.
The framework supports multi-threading & concurrency out of the box. It uses Web Workers API to spawn actors (agents) in separate threads and uses a local scheduler attached to a thread for concurrent tasks.
That's pretty neat...
FWIW, if anything is being done in JS it would definitely be written in TypeScript.
Possibly using a Rust framework like yew or percy. It should leverage the node API and be bundled along with it to make it easier to use.
Anyone interested in working on this? I probably won't get to it for a while