I mentioned a few posts ago that I consider Atom to be an important part of my static blog toolkit. It’s true: I’m writing this post with it, using the live Markdown preview. But, I’ve also been using it for day-to-day coding. I’ve been getting actual work done with it. And I’ve been enjoying it!
Atom can be extended by packages written in coffeescript - something I use currently for work - vs. elisp which I haven’t done much with since University. The truth is, though, I haven’t written any Atom packages (yet?). I’m not even sure that I will.
Because I love lists of threes, here we go:
atom
- Given my project-switching habits, I’ve long envied the Textmate/Sublime users launching a project (with tree view!) from the command-line. I can now start working on a project by typing atom ~/Projects/<name>
and it even remembers which files were open. Projectile has similar project-focused features, but I’m loving a window per-project.apm
(and stars) - Package management for years was a major pain for emacs. While it’s gotten much better lately (and I have enjoyed Cask), apm
is proving to be far more useful. Moving between machines? Star the packages you use on atom.io and run apm stars --install
.I don’t know that I’ll ever give up Emacs completely (and I actually use Vim for quick edits), but I have a new, free, cross-platform editor that I like to use - and it’s not even 1.0 yet.
]]>