Why I Still Use Vim
These kinds of comparisons always seemed a bit silly to me.<p>It&#x27;s like complaining that opening a 6MB file in windows took over 3GB on my system! (ignoring that most of that is the OS getting ready to do other things, and enabling the OS to do things other than opening and reading a 6MB file).<p>Yes, Atom isn&#x27;t the most resource friendly editor out there, and nobody is claiming it is. But it is one of the more capable editors out there. That 1GB allows for things like easy theming, inline image viewing, styling&#x2F;theming via CSS, plugins&#x2F;extensions written in a web language (which many of it&#x27;s target demographic use), complete freedom for plugins to do almost anything and everything, a full web browser for easily rendering markdown&#x2F;websites-in-progress&#x2F;documentation&#x2F;etc, code linting, compiling, debugging, decompiling, etc...<p>Not to mention that a 6MB file is pretty fucking big for something like atom. Yes, I know, 6MB isn&#x27;t &quot;big&quot;, but for an editor which is designed to only work on source files which are AT MOST a MB, it&#x27;s big.<p>If all you are going to do is open a 6MB file with none of that, then stop using it, and stop acting like it&#x27;s bad software because it doesn&#x27;t cater to your needs. Vim won&#x27;t show me 4 panes with ES2016 in one, the compiled version in scrolling-lockstep with the ES2016 pane in the next, and a visual preview of the page as it currently is in the 3rd, and the documentation to a function i&#x27;m working on in the 4th. That still doesn&#x27;t mean it&#x27;s bad software, just that it&#x27;s not a good fit when compared to the alternatives for me.<p>Stop complaining that the hammer is better than the screwdriver because it can hammer in nails better.