News for hackers. Stuff that matters.
Re:Atom text editor 1.4 released by toddmorey on Thursday January 14, 2016 @11:52AM (#10902557)
That seem pretty atypical... I'm trying everything I can think of, and I can't get the CPU above 40% utilization (and that was just a temporary spike while searching a massive directory of files).

For me, Atom idles at 0.5% CPU. 10 files open, 130MB of memory being consumed.

I'm fairly sensitive to slowness for an editor. Earlier versions of Atom had too much noticeable lag. Recently, though, it seems pretty performant.

Re:Atom text editor 1.4 released by vonklaus on Thursday January 14, 2016 @12:21PM (#10902761)
Here is a way to reproduce an issue. Put syntax highlighing on discover.

Open a 1000 line json file. Most of the issues are on syntax highlighting. The editor has a very bad way of inplementing this, based on it always crashing or timing out.

Problem is fixed if sh is plaintext

Re:Atom text editor 1.4 released by vonklaus on Thursday January 14, 2016 @03:18PM (#10904112)
The edit window closed, but to be fair I need to mention that the from 1.3 - 1.4(the new update), I opened the exact file I had significant problems with.

The editor used to bottle neck, hang, and usually would just quit after being non-responsive.

This has been fixed. The editor would take ~45-60 seconds (I timed it when i logged the issue on github). It now takes ~3 seconds. Sublimetext comparatively, is a bit better at <3 seconds, atom takes about 3-5 seconds and shakes out the highlighting over another 1 or 2. In total, you can start working on the file in about 4 seconds which is a big improvement over never/1 minute.