Why I switched to Visual Studio Code

I used to be a Sublime Text user, and used to always go back to Sublime after trying out other editors. I actually bought a license for $70 even though I could do away without it. I bought it to encourage the developers to keep on improving Sublime.

But Sublime's development seems to be slow, but at least it is stable. The only caveat is that some of the plugins isn't working as intended (ie. lack of code completion even with CodeIntel, etc.) so I always tried out other text editors and an IDE.

I first tried out Adobe's Brackets. I liked the features, but it was too slow that I decided to switch back to Sublime.

The next text editor I tried out was Atom, which was way quicker than Brackets, but still struggles to load larger files. It felt like a slower Sublime Text, which is why I again went back to Sublime.

And then came WebStorm. It was perfect. Great code completion, integrated terminal, and the refactoring tool was really handy. The initial launch was slow, but was forgivable since it's pretty quick after that. I would've bought a license for it... but came Visual Studio Code.

Visual Studio Code had all the advantages of WebStorm, but is free. It's leaner than WebStorm in terms of memory usage, is quicker to launch, and behaves like an IDE. It's as quick as a text editor, but as powerful as an IDE. Note that it also uses Electron, just like Atom, but it could load larger files (it can even load a file with more than a million lines) unlike Atom.

You get intellisense (Code Completion), refactoring, Node JS debugging, an integrated terminal, an integrated Git tool, and jumping into symbol definitions is as quick as what you would get with WebStorm.

Even the Go Plugin was really neat, wherein it could detect all the packages that I added in my GOPATH.

I feel that Microsoft did it right on this one, and I never thought I would say that I actually like "Visual Studio".

comments powered by Disqus