The state of building user interfaces in Rust

I've done professional GUI programming and there are really only three options that make sense: 1. Write the GUI natively per platform. This is best from a UX perspective but is expensive and you probably need different developers working on different platforms. Other downside is that really advanced functionality is harder to implement and sometimes the performance of native APIs is poor and hard to improve (Apple has this problem frequently). 2. Use a cross-platform framework like Qt (Electron would…

Throwing in my vote... I've been doing everything with wasm-bindgen/web-sys, i.e. just doing my UIs in html, and for 99% that's what I'd want anyways. Web UIs are portable, remotely accessible, and don't require installation on each client. For the small percent that's left where speed is critical, I've just been using wgpu and wgsl-bindgen directly. I can't think of what I'd want a native UI solution for. And then having to deal with porting it to iOS, Android, Windows…

I have this dream where I'd be able to write an application once in Rust (be it simple game, CRUD, chat, whatever) , target WASM and have users be able to run it (via browser) on desktop, android, or iOS and not have to write the program 4-6 times for different OS's. However - seeing some people diving into the WASM details makes me wonder whether it will be the way the browser implement WebAssembly that stops us from doing…

Popular in 2021 (205 points, 189 comments) https://news.ycombinator.com/item?id=27782337