Robby on Rails: 8 Things Github’s Atom Editor is not going to solve for youthoughts.sort_by{|t| t[:topic]}.collect tag:www.robbyonrails.com,2005:TypoTypo2014-02-27T23:00:30-05:00Robby Russellurn:uuid:7f67f0c6-c988-4ab3-90a2-95d316076a872014-02-26T12:46:00-05:002014-02-27T23:00:30-05:008 Things Github’s Atom Editor is not going to solve for you<p><img src="http://robbyonrails.com/files/atom_logo.jpg" alt="" /></p>
<p>We’re all excited about the prospect of a new code editor (<a href="http://atom.io">Atom Editor</a>). We all love what <a href="http://github.com">Github</a> has produced so far and our expectations for anything new are going to be quite high.</p>
<p>Do we know exactly what it’ll be yet? Not quite. We have some hints… but until it’s released… <a href="http://www.robbyonrails.com/articles/2014/02/25/github-prepares-to-release-atom">we’ll continue to speculate</a>.</p>
<p>While I am not one to make predictions—I do have a few theories about what Atom will <em>not</em> do for us. (if you’re looking for a new business idea… feel free to snag any of these)</p>
<p>1. <strong>Atom Editor will not make it easier to code while in the shower.</strong> While I would love to take advantage of putting my thoughts to code while letting my conditioner do it’s thing… I don’t believe they’re trying to solve this problem (yet).</p>
<p>2. <strong>Atom Editor is not going to make it difficult for me to produce shitty code.</strong> To date, nearly every code editor on the market is focused on making it easier to produce code…. good <span class="caps">AND</span>/OR bad. Where is the editor that tells us to quit while we’re head. “Are you serious, Robby? Have you seen what you’ve been writing today? Just stop. Go outside. Take a break and try again tomorrow.”</p>
<p>3. <strong>Atom Editor will not bring synergy to developers.</strong></p>
<p>4. <strong>Atom Editor will not change the music playing</strong> to compliment the coding problem that I’m faced with. If my tests aren’t passing… I wish my music would keep me calm and focused. This is not a time to start playing <span class="caps">WHAM</span>! (…or maybe it is)</p>
<p>5. <strong>Atom Editor will not bring about peace in the Emacs vs Vim wars.</strong> We are going to have to let them sort a peace deal on their own.</p>
<p>6. <strong>Atom Editor will not have integrated <span class="caps">CVS</span> or Subversion support</strong> when it is released.</p>
<p>7. <strong>Atom Editor will not promise the world to you</strong> like Visual Studio.NET did back in 2002. I remember their demo videos and it seemed like the development world was about to change! I never would have guessed that come 2005, I’d be in love with something as simple and fancy-feature-less as TextMate.</p>
<p>8. <strong>Atom Editor will not just be a clone of Sublime Editor</strong>. Github has too clever a team for that objective.</p>
<p>What are you confident that Atom Editor will <em>not</em> be?</p>
<h2>Update</h2>
<p>8 for 8!</p><p><img src="http://robbyonrails.com/files/atom_logo.jpg" alt="" /></p>
<p>We’re all excited about the prospect of a new code editor (<a href="http://atom.io">Atom Editor</a>). We all love what <a href="http://github.com">Github</a> has produced so far and our expectations for anything new are going to be quite high.</p>
<p>Do we know exactly what it’ll be yet? Not quite. We have some hints… but until it’s released… <a href="http://www.robbyonrails.com/articles/2014/02/25/github-prepares-to-release-atom">we’ll continue to speculate</a>.</p>
<p>While I am not one to make predictions—I do have a few theories about what Atom will <em>not</em> do for us. (if you’re looking for a new business idea… feel free to snag any of these)</p>
<p>1. <strong>Atom Editor will not make it easier to code while in the shower.</strong> While I would love to take advantage of putting my thoughts to code while letting my conditioner do it’s thing… I don’t believe they’re trying to solve this problem (yet).</p>
<p>2. <strong>Atom Editor is not going to make it difficult for me to produce shitty code.</strong> To date, nearly every code editor on the market is focused on making it easier to produce code…. good <span class="caps">AND</span>/OR bad. Where is the editor that tells us to quit while we’re head. “Are you serious, Robby? Have you seen what you’ve been writing today? Just stop. Go outside. Take a break and try again tomorrow.”</p>
<p>3. <strong>Atom Editor will not bring synergy to developers.</strong></p>
<p>4. <strong>Atom Editor will not change the music playing</strong> to compliment the coding problem that I’m faced with. If my tests aren’t passing… I wish my music would keep me calm and focused. This is not a time to start playing <span class="caps">WHAM</span>! (…or maybe it is)</p>
<p>5. <strong>Atom Editor will not bring about peace in the Emacs vs Vim wars.</strong> We are going to have to let them sort a peace deal on their own.</p>
<p>6. <strong>Atom Editor will not have integrated <span class="caps">CVS</span> or Subversion support</strong> when it is released.</p>
<p>7. <strong>Atom Editor will not promise the world to you</strong> like Visual Studio.NET did back in 2002. I remember their demo videos and it seemed like the development world was about to change! I never would have guessed that come 2005, I’d be in love with something as simple and fancy-feature-less as TextMate.</p>
<p>8. <strong>Atom Editor will not just be a clone of Sublime Editor</strong>. Github has too clever a team for that objective.</p>
<p>What are you confident that Atom Editor will <em>not</em> be?</p>
<h2>Update</h2>
<p>8 for 8!</p>