Switching to Github’s Atom

Ever since I started to write code, I searched for code editor that worked best for me. From Notepad++ to Adobe Dreamweaver, I jumped from editor to editor in search for the “perfect fit”. Then I came over Sublime Text.

After I downloaded and installed Sublime Text, I immediately fell in love with it. From being able to customize the theme to the ability to add whatever plugins you needed into the editor, everything felt right. But as I always try to improve myself, I started playing with Git and Github for version control. This is when I ran into some kind of problems. I tried to find some plugins to integrate Git with Sublime for a better workflow and failed. Enter Github’s Atom.

First time I tried Atom, it was still in beta. I had high hopes for it. But it was a failure, as the load time was very high, some bugs showed their heads; it wasn’t working nice at all. So I continued using Sublime as my code editor. Fast forward a few months, Atom was finally out of beta and, naturally, I gave it a second chance. I was blown away by how well it worked now, so it became my main code editor to this day.

Not to get me wrong, I’m not saying that Sublime isn’t a good code editor. If it wasn’t, I wouldn’t have purchased a license for it. As a matter of fact, I still use Sublime when I need to open a single file to view or quickly edit something. But with projects I work on,  I love how Atom opens the entire project and keeps track of edits, additions or even deletions in the source code, at the file level. And the fact that it’s free doesn’t hurt either.