I try Atom every couple of months but never last long before heading back to my terminal. I'm assuming it's only a matter of time though before it's polished and fast enough that we'll see a lot of converts.
It may be that its worth the effort - I wouldn't know. But the feeling that I'm not actually improving things by moving to an editor that can't handle big files is just too prevalent.
So I inevitable switch back to ST3 and go back to work, every single time. Sorry Atom guys, its just not working for me.
It uses regex with some off-the-wall engine that they chose because it supports just about every encoding under the sun. Many of the language syntax packages I looked at could easily improve their regex performance.
Plus when you open a file as "plain text" or disable the syntax highlighting package much of the sluggishness goes away.
I'd love to dive in and try and fix it myself but I won't have time to for a few months. The code itself isn't horrible just a little undocumented.
My personal guess is that is because Code might use a more stream-like processing of the source files and does not have the whole files in memory (it also works with really big files - which Atom does not support) and that this does work better
You are probably right about the streaming system. It's interesting that atom doesn't do it that way (seeing as how streams are such an useful part of "server-side" javascript)
Like I said at one point i'd really like to dive into this stuff and spend some time trying to figure out exactly what the problem is (and maybe help find a way to fix it).
Trying to get permission to setup some kind of VM on the machine, (likely VB) so I can use what I'm used to.