My laptop often sounded like it was about to take off, because the fans were always on while I was coding, and it was prone to freezing and crashing when I tried to navigate the folder directory.Īround this time, I heard more and more positive reactions from colleagues and developers on my Twitter feed about VS Code. However, I began working on Magento 2 projects, which contained a lot of files (mostly backend PHP) and this meant that Atom’s performance started to suffer on my MacBook. I added my own code snippets, changed the colour contrast to make things easier to read, had a collection of favourite packages, and even developed some packages of my own for it (even releasing one: rainbow tree). It was open-source, which made me feel virtuous, developed by a company that I admire (GitHub), and I loved being able to customise it (even though I only ever used a slight variation of the default colour theme!). Back then, Atom was relatively new and shiny, which was all the reason I needed to choose it! (developers can be fickle) So I downloaded Atom and started the irritating period of learning new software: relearning keyboard shortcuts, locating menu items and working out how to customise settings. Even in 2016, I felt like Sublime Text was a little dated and that there were more up-to-date alternatives. I had just finished a role where I used IntelliJ, but I wasn’t in love with it, and I wanted to use an editor that didn’t require a licence. I started a new job in 2016 and needed to install a code editor to my new laptop. It’s been six months since I made the full-time switch to Microsoft’s VS Code, which I thought was a good point to reflect on the experience so far. But after seeing so much positive reaction to VS Code, I decided it was time for a change. I’ve been a long-time user of GitHub’s Atom, using it as my primary code editor for three years (and three years is a lifetime in the world of frontend development right?).
0 kommentar(er)
