The way I'd love to see this work out for Rust/WASM is: 1. Create browser bindings 2. Create fs/net bindings to Node 3. Iterate, iterate, iterate 4. APIs for net, fs, DOM are formalized through WASI 5. Roll out smaller runtimes with only the WASI APIs
-
-
Show this thread
-
I'm not at all advocating this as a replacement for any existing work by the way. It just seems to me that if the goal is to provide a premier UI development experience for Rust, targeting an existing platform might be the fastest way to get there. Esp. one with a WASM runtime.
Show this thread
End of conversation
New conversation -
-
-
Just thought I'd mention the Tauri project https://tauri.studio in case you're not aware of it. Hasn't got wasm support yet but roadmap suggests it might not be far off.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
people say the dom is slow, its a lot faster than anything i managed to build without having to worry about js or css..
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Have you seen Azul? https://azul.rs/
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.