Skip to content

Instantly share code, notes, and snippets.

@lodestone
Created February 27, 2014 20:00

Revisions

  1. lodestone created this gist Feb 27, 2014.
    27 changes: 27 additions & 0 deletions 5-reasons-to-avoid-atom.markdown
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,27 @@
    # 5 Reasons You Should Avoid Github's Atom Editor

    ### 1. There's a Big Hoopla

    It must be a passing thing. Just trendy teenagers hopping on the bandwagon. Another fad from an industry that is addicted to it. It must be these things, despite Github's six years of work on it before release. It must be worth avoiding despite the fact that obvious thought, time, and love has been put into the project.

    ### 2. It doesn't do *X*!!!

    Yeah, it doesn't do *X*. It does Y and Z really well, but because it doesn't do *X* *yet* it must be eschewed. End of story.

    ### 3. It isn't (*fully*) Open Source

    Why would anyone make software in today's day and age that has some sort of *business model*? For shame, Github, for shame. Github - we know you really grok open source **AND** have also built an amazing business. But combining the two? Your efforts to create the next generation of text editing is just unthinkable.

    ### 4. It's a Blatant Rip-off of Sublime Text

    Yeah, Atom is just like Sublime Text! Well, except for the core of it being web technology, instantly hackable, and javascript and node being the language for extensions and plugins, rather than python. Oh, and wait until you hear this: Github even ripped off *VIM* with a plugin called *vim-mode*!!!

    ### 5. Atom Sends Data to Google Analytics

    Aghast! You wily Github. How dare you, DARE YOU, try and collect statistical and diagnostic data that will probably be used for improving the product?!!



    ## Conclusion

    Hush yourself. Hug yourself. Breathe - it will all be okay.