BUT.... it is way, way better than it used to be. I keep it installed and use it from time to time, to let it update itself and see how it has grown.
It clearly has momentum, and computers clearly are getting faster... probably one day the slowness of it won't matter. But it still matters today -- Atom is noticeably slow on the fastest Mac notebook you can currently buy.
Running on a stock mid-2011 Air w/ 4GB Ram plus a Thunderbolt display. If it was slow, I would have switched or upgraded my machine sometime ago.
Things that are slow to me are waiting for node-sass to compile on save, server-side code reloading, npm installing... and so on.
I usually have one long-lived instance of an editor for the project/thing I'm focusing on, but I also frequently fire up "temporary" instances for one-off editing jobs, from the terminal.
The difference between, let's say, "subl ." (launch Sublime Text in the current directory) and "atom ." is staggering: Sublime Text starts instantly with a boatload of plugins; Atom starts nearly instantaneously but then takes around 5 seconds to become usable, without plugins, after repeated runs.
(Speaking of specs, I'm on a late 2013 Retina MacBook Pro, 16 GB of RAM)
I must be more tolerable to that startup time, perhaps I've even become used to it.
My recommendation is to give Atom a chance, see if it fits into your workflow (whether it has native support for the languages/frameworks you work in, or if packages exist). If it works out, then you have a viable alternative to ST3 :)
I really did not enjoy writing plugins for sublime. The development/debugging/testing experience isn't especially pleasant.
That said, the new features (.sublime-syntax files instead of TM files, etc.) look very refreshing.
https://github.com/atom/atom/issues/5344 https://github.com/atom/fuzzy-finder/issues/57
Fortunately, I have a concrete solution: copy what Visual Assist does. Space-separated substrings. It makes it very easy to be more precise about what you're looking for, while still letting you be vague when you'd rather, and the computer never has to make a judgement call.
See here: http://docs.wholetomato.com/default.asp?W193 and search for "filtering in the dialog" (their page has no anchors! - I'm certainly not suggesting you should copy their HTML style)
It's certainly a slower editor - I have found that opening it, creating a new window, and quitting all take more time than I would like. However, I have stuck it out primarily for two reasons:
1. It's far more extensible. Sublime Text has a thriving package ecosystem, but the limitations of the extension API show up in lots of little places. Atom being browser-based comes with its downsides, but it also allows flexibility that Sublime could only dream of.
2. It's open source. Sublime Text is a great editor, but it's closed source, maintained by a single guy, and updates have slowed to a crawl. It's not something I ever felt 100% comfortable with relying on as part of my day-in-day-out workflow.
Granted all my devices use SSDs, but still for me it's been like 10 seconds at the worst, and currently it opens in like 3-4 (and i have about 30 plugins too)
The speed issues are all but gone imho (start-up is a bit slow, but I have it open almost all the time so I hardly notice).
The main reason I switched was because Atom is FOSS, and that always bothered me about ST3. It's also very easy to hack on, which is nice as well.
(I've held off upgrading because I've always been in the middle of a project... but I'm now realising that I really am just always in the middle of a project, so I might as well just get it over with.)