News for hackers. Stuff that matters.
Re:Introducing Atom-IDE by 482794793792894 on Tuesday September 12, 2017 @01:52PM (#15229546)
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.
Re:Introducing Atom-IDE by dotancohen on Tuesday September 12, 2017 @02:34PM (#15230128)
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.

Re:Introducing Atom-IDE by opencl on Tuesday September 12, 2017 @03:27PM (#15231079)
This is actually backwards: Electron was originally created for the Atom project and even used to be called Atom Shell.
Re:Introducing Atom-IDE by dotancohen on Thursday September 14, 2017 @03:55AM (#15245800)
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.

Re:Introducing Atom-IDE by ForHackernews on Tuesday September 12, 2017 @03:17PM (#15230891)
> 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...