Switch to VSCode from Atom

Atom as a code editor just becomes slower and slower with the burden of massive plugins, requiring near 15s on my MBP to initially display file contents. In comparison, VSCode with similar extensions just takes 5s to show file text upon launch. There must be some architectural issues in the Atom startup process, as both are based on Electron. The memory/cpu footprint also has huge differences as this old post shows. Atom sometime even stops responding and asks to wait for editor window to run.

While speed performance is an important factor, all kinds of mysterious long pending bugs are really killing it. In my scenario, the vertical scrollbar sometime just turns into a white bar. Some issues are reported, analyzed, but just doesn’t reach a fix. And the git interface cannot stage lines for files with unicode filename, but only able to stage the whole file. The nuclide file tree is unusable which steals text editor focus! All of such problems are long existed nuisances to bear with.

Fortunately, VSCode now also enjoys the affluence of extensions. Almost all of my Atom plugins find their counterparts in VSC. The only advantage of Atom is the beautifulness in contrast to the VSCode default theme’s coarseness (the blue status bar is horrible), but hopefully the Atom One Dark theme and keymap extensions are the cure.

Just after Microsoft successfully bought Github, it seems the right time to switch from Atom to VSCode finally.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.