There's also the problem that Atom doesn't have any debuggers worth speaking of so far. That could change now.
I'll have a look into this. Sounds great anyway.
That being said, the performance has been getting steadily better, enough to the point I can do most of my coding in it without noticing a problem. I'd suggest giving it another go and see how it does for you! It's quite a joy to hack on.
I do still resort to vim on the command-line for some things, but as a "daily driver" code editor, Atom has been excellent.
I've noticed that the editor, with my load of plugins, comes up relatively quick on OSX (~4 seconds from launching, equally as long to open a new window), and roughly twice as slow on Windows (~8 seconds from click, ~3 seconds to open a window)
But, when I'm using it, I'm basically living in the app, so the startup time is really a moot point IMO.
Restarting made it end up in the same install cycle as before.
Atom fixes what is broken in Sublime, but has it's own issues that are currently far worse.
I just ran a find over the project I've been working on full time, and the largest file, by a long shot, is 8kb, and a little under 100 lines. That's just an autogenerated enum of the HTTP status codes though, so it isn't indicative of real code.
In the vast majority of cases, all of my files are less than 4kb, and hover around 40 lines or so. Atom handles this use case just fine, and I'm hard pressed to think of a situation where I'd run into performance concerns. The entire process itself is using less than 80mb of RAM, and 0.2% of my CPU. A single tab of Chrome is worse than that.
What are people doing with their text editor that they need blazing speed?
I admit the answer that immediately comes to mind is: "uh, editing text?" But to be more serious --
My own coding projects rarely have files with more than 300-400 lines, but the coding projects I'm working on aren't always my own, and my own projects involving text files aren't always coding. If I have reason to load a 3000-line source code file, I don't expect my editor to choke. (I've done this on occasion.) If I have reason to load a 603K, 7300-paragraph Markdown file, I don't expect my editor to choke on that, either. (For somewhat obscure reasons, I'm doing that weekly, and yes, I'm making edits as I go.)
In (very!) limited testing just now with both those cases, Atom 1.4 seemed to do just fine, for the record.
All new code is ES6: https://twitter.com/nathansobo/status/670047510258253828
It's a task that could easily be spread across any number of human translators, too.
The main limiting factor is the quality of the test suite, which dictates how quickly typos could be found.
