3 ms·
I might be wrong here so someone correct me but I believe it's because every time you open a new electron app, you are opening another instance of Chrome. So if
by _fat_santa 5y ago
I might be wrong here so someone correct me but I believe it's because every time you open a new electron app, you are opening another instance of Chrome. So if you have Chrome, VSCode and Figma running, that's 3 instances of Chrome each eating their respective 2-3GB of memory and associated CPU cycles.
- torginus 5y agoYou are not wrong, but there are multiple billion dollar companies that build their products on top of Electron. Presumably they could afford to hire engineers or Google could step in and optimize Chrome's renderer for Electron's use cases. I may be wrong, but as things are now, Electron, more or less packages an unmodified, headless Chromium.
- beardyw 5y agoYes, and if you allow it, an Electron app can just open the chrome debugger you know on the browser part of the app. There is a messaging system between that and the node part, to provide stuff like file access.
- lenkite 5y agoFundamental architectural decisions in the Chromium code cannot be solved via patching no matter how many billions are thrown at it. Would likely need a large rewrite which is effectively a new project.