22 May

What Programs Do I Use: GitHub’s Atom

As I said in this post, I’m doing a series of blog posts about the programs that I use on Ubuntu.

My first program that I want to talk about is GitHub’s Atom code editor.  I tired a few code editors (mostly with working with Markdown) and none of them is as awesome as Atom.  Why?  See below:

In the first screenshot  on the left, you can see that I’m working on Ubuntu Membership workshop (that I plan to do a bit before the global jam or after it). The first panel on the left is the file manger for that specific project.  The middle is the editor where there is syntax highlighting happening for Markdown.  And on the last panel on the right, is the Markdown preview for that file.

In the next and final screenshot on the right, you can see the same file being worked on but in the middle panel shows what I have added (in green), deleted (in red), and changed (dark yellow) after the last commit.  It’s a handy feature.

I only have used Atom for a week now, and I don’t have much to say since I only work with Markdown files at the moment.  But that will change as I start to work on my coding projects, as stated here.  I know that Jono Bacon wrote an amazing post on Atom where I know that I will check out those other features and maybe report on them here.  Most likely, I will have a follow up post once I start to code more.

As for this series, I will post one post every Sunday until I run out of programs to talk about.  The next one that I will talk about is Mudlet, a M* client that I use to play my favorite text-based online roleplay.

See you next week!

2 thoughts on “What Programs Do I Use: GitHub’s Atom

  1. Good choice. Make sure to install “activate POWER mode” 🙂

    You won’t regret it (it makes coding so much more fun – every key stroke is an explosion of power!)

    P.S. I’ve been using Atom regularly now for about the same amount of time (a week) and I can’t believe how comfortable it is. Before that for my web design projects I used Bluefish (good – but not updated often enough and could *really* do with some polish).

  2. My humble opinion is. Start using one tool and learn it in deep. If it works for you don’t change the tool just to be cool.

    For example I love Vim and would never replace it with any other text editor. I am million times more productive with Vim. But for someone not used to Vim you can get 10-times less productive with Vim quite easily, especially if you don’t know how to type with 10 fingers.

    This is good article why I use Vim: “Why Atom Can’t Replace Vim”: https://medium.com/@mkozlows/why-atom-cant-replace-vim-433852f4b4d1#.bb48dnn8f

Leave a Reply

Your email address will not be published. Required fields are marked *