Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I really don't think the problem is Electron, or even JavaScript.

I think the problem is Chrome, which the Electron runtime requires. Each separate Electron app has its own copy of Chromium in memory. (What happened to shared libs?)

I see two ways you can help:

(1) you can try to get memory-usage-reducing fixes into Chromium, or,

(2) you can build an Electron-compatible runtime that uses less memory (maybe by transpiling it into code that runs on a native toolkit, and not having a static copy of that runtime per-app).



Someone posted a link to a new framework called Proton Native... that's a great step in the right direction




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: