Disagree, Electron-based apps are known for being memory and CPU hogs; if we want our laptops to run cool and for batteries to last a long time, we need to move

Disagree, Electron-based apps are known for being memory and CPU hogs; if we want our laptops to run cool and for batteries to last a long time, we need to move things to native code. I think the "new protocol" example is particularly good one - things like IPFS run complex daemons under the hood and might access gigabytes of data, while their interface to browser is relatively simple: a channel which takes small requests and returns medium-sized responses. It's ideal case for moving to native code. (Of course it has its own downsides too, like losing ability to run same codebase on the web. So far, I've been avoiding Electron's usage by running web versions instead - Slack-on-the-web is just as featureful as Slack-in-Electron, but shares memory with my main browser. But for other applications, native code should be a plus)