4 ms·
Most of the time though, the real issue that people have with Electron-based apps is memory and CPU usage. Electron is notorious for hogging RAM like there's no
by Etheryte 10y ago
Most of the time though, the real issue that people have with Electron-based apps is memory and CPU usage. Electron is notorious for hogging RAM like there's no tomorrow. While this project is a neat idea, it doesn't seem to address the main problem of Electron.
- pavlov 10y agoUsing the system web runtime does reduce the app's memory usage too, not just the on-disk size. The system runtime is loaded just once (and is probably already in active memory), whereas each Electron app loads its own copy of Chromium. For large apps, it won't make a huge difference. I'm absolutely not saying Atom or Spotify should switch away from Electron... The use case I had in mind for Electrino is more about small utilities, desktop widgets, that kind of thing.
- fox8091 10y agoImho, it will make a big difference for large apps too, especially on CPU usage. Chromium is what takes up the majority of CPU time, so by reducing it to a very small replacement, it should help.
- ricardobeat 10y agoHave you tested that? In my experience using a system webview actually consumes more resources than Electron, and is noticeably slower, at least in OSX/WebKit.
- pavlov 10y agoI did do trivial tests. The Electrino "Hello World" launches faster and consumes about 70% less memory than the Electron one. For complex apps, I imagine the picture can be very different. The use case I see for the Electrino approach is small apps that are constantly loaded. Big productivity-style apps are better served by Electron.