You may be happy to hear that the new Fedora installer is using Firefox under the hood. Ephemeral profile dir on startup, plus custom userChrome.css to hide most of Firefox UI, and I couldn't tell a difference between it and Electron.
Tauri apps take advantage of the web view already available on every user’s system. A Tauri app only contains the code and assets specific for that app and doesn’t need to bundle a browser engine with every app.
Rendering will still use Edge/Chromium on a generic Windows machine.
Looking at firefox memory usage, i’m afraid the issue there is not memory safety but rather the average javascript developer being completely and blissfully unaware of and careless about memory memory usage of the software they write
It'd be interesting to understand how much of that memory pressure is down to the devs compared with the frameworks now trying to cache everything in sight.
React Compiler automatically memoizes values and functions, reducing the need for manual useMemo calls. You can use the compiler to handle memoization automatically.
This would have changed so much. Desktop apps powered by the engine of Firefox not Chrome.
Why? Not enough company buy in, not enough devs worked on it. Maybe developed before a major Firefox re-write?