
To me, Vim comes close to being the perfect editor and I probably won’t need to switch ever again. The learning curve is very steep and it took me a year to master it, but investing time to be truly comfortable with my #TextEditor was more than worth it. I wanted to "look like a hacker" by doing everything inside my terminal and by becoming a better Unix citizen.it is a reliable tool that has been around for more than 30 years and will still be around for the next 30 years.your fingers literally don’t ever need to leave the keyboard home row (I had to remap the escape key though).After 3 years of wearily moving my arm and hand to perform the same repetitive tasks, I decided to switch to Vim for 3 reasons: I extended the editor with custom Python scripts that improved keyboard navigability such as autofocusing the sidebar when no files are open, or changing tab closing behavior.īut customization can only get you so far, and there were little things that I still had to use the mouse for, such as scrolling, repositioning lines on the screen, selecting the line number of a failing test stack trace from a separate plugin pane, etc. I guess the perfect editor would be Atom without any of its flaws but it’s not quite there yet.I liked Sublime Text for its speed, simplicity and keyboard shortcuts which synergize well when working on scripting languages like Ruby and JavaScript. The speed/performance factor is really something that comes across most reviews of Atom out there sadly. It’s overall rather slow and unstable (you will notice that if you’re working all day long on your text editor). My verdict Although it comes packed with great features and an overall neat layout, Atom is still having lots of difficulties handling large files and keeping a low CPU usage. Strange syntax management sometimes, you get a different color for your variable name depending on what you typed before ( const, let, var etc.).Most of the core is written in CoffeeScript, but the Github team is transitioning to ES6.Project manager possibilities are a bit limited but plugins can fix that.It’s a browser-based app (runs on Electron), and is a bit slow to load and sometimes to respond. Has some issues handling large repos/folders and CPU usage can go pretty high.Takes some time to get the right setup.Is there an active community of users/programmers feeding the beast? How often does it get updated?Īgain, this post reflects my opinion, so I don't expect everyone to agree. How many plugins/themes/packages are available? How heavy the program is on your hard-drive, on your RAM too?


Can it handle large repos without crashing? So in order to make that list up, I considered the following factors for each editor: You're not married to your text editor (sorry Brackets 💔, you made me very happy for a while but I needed some new perspective on things and your syntax highlighting is crap) and you don't have to always work around a missing feature or a crappy CPU usage (you know I'm talking about you Atom). So it should not be picked lightly and you should even re-consider your choice every once in a while.

Your programming style (indenting, syntax, preprocessing, spaces, comments, etc.).Your text editor will have a tremendous impact on:
