Locally, I've tried Atom every now and again and even with the new improvements in 1.1, as soon as you get above a certain threshold in number of lines it starts to slow down considerably (>= 250ms key-press, subjectively) which would only be acceptable if I was running in the browser and even then would be barely useable. Come to mind, the cloud9 ide feels 'snappier' that Atom.
In Vim I can just open up a 21mb db dump, do some regex to delete unwanted rows, and be done after a few seconds. Its amazing how vim can handle large files. I cannot imagine doing the same in Atom.
Oh come on now, that's really exagerating.
For many tasks JavaScript might be fast enough but as your project grows and you want to fo more complicated tasks, you'll hit a wall with JavaScript.
It's a lightweight IDE (text editor really) and full console. With docker support.
Just from skimming it a bit, to handle Korean, their developer decided that Korean characters have a special unique width from other writing systems and gets that width from the cached bounding rect of a particular char as run through the engine, and then that factors into their wrapping calculations. So now they have a function called getKoreanCharWidth and are basically implementing alphabet-specific text layout in a bad way on their side of the fence. It doesn't even work particularly well, but most importantly it's obviously not a generic solution, and duplicates what the browser engine already does much better by using proper shaping and layout engines.
On the flip side, it sounds like Atom is a really cool project if you don't really know what you're doing yet and want to learn from your mistakes. Reinventing the wheel and noting it hobbles is a good way to acquire experience, and it's not like the world relies on Atom. Perhaps it also creates positive pressure to improve the APIs they're writing against, even though it's sad that happens so indirectly then.