I tried replacing Sublime Text with it, and got quite into it.
I however fell back to ST for a number of reasons.
Speed - ST is just quicker to get up and running.
I found a (large) file or two that atom just could not deal with.
State - I can CMD-Q ST with no nags, then re-open to my previous state when I want. I generally have a number of useful scraps open at one time, so not having to save these is great, and not losing them when I close the editor is just brilliant.
Visuals - The open file code overview on the RHS is a must have for me.
Muscle memory - I just kept opening ST from the terminal, and had to go through the process of closing ST and opening atom. This could have been mitigated by re-aliasing slt, but that's a commitment.
I do wish ST would automatically include the directory of the file you are opening in the project like atom. Brilliant when you are just flicking through source. Open one file and then not have to leave the editor to go to the next one.
There was also something funny when I opened a squid cached js file - I could highlight and copy the text, but whatever was copied to the clipboard was not what I had highlighted. Think highlighting and copying in general is still a bit beta.
That said, I spent some time tinkering, and loved the open nature of the plugins.
The bracket matcher plugin does both highlighting of brackets and auto closing. I hate auto closing. It took all of 15 minutes to work out the plugin architecture, disable the offending plugin and hack in the parts of it that I liked.
In my books that's a winner. I may even pick it back up if it is going to get real love from the community.
I however fell back to ST for a number of reasons.
Speed - ST is just quicker to get up and running. I found a (large) file or two that atom just could not deal with.
State - I can CMD-Q ST with no nags, then re-open to my previous state when I want. I generally have a number of useful scraps open at one time, so not having to save these is great, and not losing them when I close the editor is just brilliant.
Visuals - The open file code overview on the RHS is a must have for me.
Muscle memory - I just kept opening ST from the terminal, and had to go through the process of closing ST and opening atom. This could have been mitigated by re-aliasing slt, but that's a commitment.
I do wish ST would automatically include the directory of the file you are opening in the project like atom. Brilliant when you are just flicking through source. Open one file and then not have to leave the editor to go to the next one.
There was also something funny when I opened a squid cached js file - I could highlight and copy the text, but whatever was copied to the clipboard was not what I had highlighted. Think highlighting and copying in general is still a bit beta.
That said, I spent some time tinkering, and loved the open nature of the plugins. The bracket matcher plugin does both highlighting of brackets and auto closing. I hate auto closing. It took all of 15 minutes to work out the plugin architecture, disable the offending plugin and hack in the parts of it that I liked.
In my books that's a winner. I may even pick it back up if it is going to get real love from the community.