4 ms·

Most of the RAM use comes from its architecture (it basically runs a web browser to display the UI), so this isn't a problem that they can just address. They'd

Most of the RAM use comes from its architecture (it basically runs a web browser to display the UI), so this isn't a problem that they can just address. They'd have to rewrite the entire text editor with a different technology.

dotancohen 9y ago
So why did the developers of a text editor decide on a web browser stack for their project? Yes, I know that the answer is "electron". They picked the wrong tool for the job.
- ForHackernews 9y ago
  > So why did the developers of a text editor decide on a web browser stack for their project? When all you have is a hammer...
- opencl 9y ago
  This is actually backwards: Electron was originally created for the Atom project and even used to be called Atom Shell.
  - dotancohen 9y ago
    And it was the wrong tool for the job even then. Atom might be Electron's reason for existing, but that just emphasizes that Electron (in its current form) should not exist at all. I have no problem with the idea of using Javascript for desktop application development. I do have a problem with relying on a memory-hogging framework, which Javascript was originally design to _avoid_ because back in the 90's it was meant to run in the resource-limited web browser. Too bad that Javascript has strayed so far from its roots.