Make webserver async

[JoeyBF]

It's a bit silly to manually handle threads/channels/messages to make sure everything is quick and nonblocking when that is why async exists.

While we're at it, I suggest we integrate both the JS frontend and the Rust/WASM manager into a single crate, using something like dioxus or leptos. I expect that it will make the webserver much easier to maintain and upgrade in the future.

[dalcde]

Do they have a good story for supporting both wasm mode and server mode? I remember that being a non-trivial thing to handle when looking into options

…

On 19 July 2024 1:22:22 pm HKT, Joey Beauvais-Feisthauer ***@***.***> wrote: It's a bit silly to manually handle threads/channels/messages to make sure everything is quick and nonblocking when that is why `async` exists. While we're at it, I suggest we integrate both the JS frontend and the Rust/WASM manager into a single crate, using something like dioxus or leptos. I expect that it will make the webserver much easier to maintain and upgrade in the future. -- Reply to this email directly or view it on GitHub: #160 You are receiving this because you are subscribed to this thread. Message ID: ***@***.***>

[JoeyBF]

I'm not fluent in webapp-speak yet so I'm not 100% sure, but it looks possible or requires at most the amount of work we put in the code as it is right now.

How much do we want full-wasm mode? Is it just to serve using gh-pages? I'm thinking we can just rent a server somewhere for cheap and host there