IMO the approach MS took was actually the correct one here - use Electron for your v1, then rewrite it once things are more established. There's nothing wrong w

IMO the approach MS took was actually the correct one here - use Electron for your v1, then rewrite it once things are more established. There's nothing wrong with using a slightly less performant version of something for your MVP (could be argued against for someone as large as MS, but still). Rails is perfectly acceptable, you don't need Rust as your backend from day 1. As a separate argument, this entire point might be moot. Native webviews are becoming more common (hell MS has used them for the OS for quite a while - when I was there working on the windows 10 start menu, it was actually a webview) and can be much more performant. Since you aren't bundling a full browser in the executable, the memory impact is quite low. Tauri seems to be gaining quite a bit of traction which leverages native webviews, and shows a lot of promise.