I think it's likelier Rust will have good bindings to Electron before it has a native solution that can *overtake* Electron. Electron and the DOM are *really* good. Building something that could match it, let alone overtake it, requires an several people-years worth of work.
-
Show this thread
-
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
1 reply 0 retweets 14 likesShow 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.
1 reply 0 retweets 7 likesShow this thread -
Replying to @yoshuawuyts
One of the main reasons I hunger for a non-Electron solution is how much resource consumption and (in)security surface area it pulls along for the ride, so embrace-and-hope-to-replace doesn't seem to offer much short-term benefit other than gaining Trojan-horse-style mindshare.
1 reply 0 retweets 0 likes
But Electron is rather efficient? When idle it consumes no cpu, and RSS by default is fairly low as well. Not shipping a DOM has many tradeoffs, not in the least cutting corners on accessibility, being able to publish cross-platform, or lack of development tools.
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.