5 developers explain why they use Visual Studio Code [Sponsored by Microsoft]


Visual Studio Code has quickly become one of the most popular text editors on the planet. While the debate will continue to rage over the relative merits of each text editor, it is nonetheless true that Visual Studio Code is unique in that it is incredibly customizable: it can be as lightweight as a text editor or as light as a text editor. feature-rich than an IDE.

This article is one of a series brought to you in collaboration with Microsoft. Download Learning Node.js Development for free from Microsoft here.

Try Visual Studio Code yourself. Learn more here.

This means that the lineup of developers using Visual Studio Code is incredibly diverse. Each faces a unique set of challenges alongside their personal preferences.

I explained to a few of them why they use Visual Studio Code and how they make it work for them.

“Visual Studio Code is streamlined and flexible”

Ben Sibley is the founder of Full themes. He likes Visual Studio Code because it’s relatively lightweight while still providing considerable flexibility.

“I love how streamlined and flexible Visual Studio Code is. Personally, I don’t need a ton of features from my IDE, so I appreciate the simplicity of the default setup. There is a very concise set of built-in features like Git integration.

“I used PHPStorm before and while it was really feature rich it was also overwhelming at times. VSC is faster, lighter and with the extension market you can choose the additional tools you need. And it’s a publisher popular enough that you can usually find a reliable, well-reviewed plugin.

Read more: How Visual Studio Code Can Help Bridge the Gap Between Full-Stack Development and DevOps [Sponsored by Microsoft]

“Visual Studio Code is the best in terms of extension ecosystem, language support and configuration”

Libby Horacek is a developer at Position development. She has worked with several different code editors, but has struggled to find one that allows her to effectively switch between languages. For Libby, Visual Studio Code offered the right level of flexibility.

She also explained how the Position Development team used VSC’s Live Share feature which allows developers to share and collaborate directly on code in their editor.

“I am currently using Visual Studio Code. I have tried a LOT of different editors. I’m a multilingual developer, so I need an editor that’s not just for one language. RubyMine is great for Ruby and PyCharm is good for Python, but I don’t want to switch editors every time I switch languages ​​(sometimes multiple times a day). My main constraint is support for the Haskell language – there are now plugins for most IDEs, but some are better than others.

“For a long time I used Emacs just because I was able to steal a great config setup from a colleague, but a few months ago it stopped working due to updates and I didn’t want to acquire the expertise of Emacs to fix it. So I tried IntelliJ, Visual Studio, Atom, Sublime Text, even Vim…

“My team also uses Visual Studio’s Live Share for the match. I haven’t tried it personally, but it seems like a great option for remote pairing. The only thing my colleagues have warned about is that they encountered a bug with the “Undo” feature that erased most of a file they were working on. Maybe this bug has been fixed now, but as always, engage early and engage often! “

“As a JavaScript development store, we love that VSC is written in JavaScript”

Cody Swann is the CEO of Gunner technology, a software development company that uses JavaScript on AWS for the public and private sectors.

“All our developers here [at Gunner Technology] use VSC.

“We switched from Sublime about two years ago because Sublime started to feel sluggish and sloppy.

“Before that, we were using TextMate and dropped it for the same reasons.

“As a JavaScript development store, we love that VSC is written in JavaScript. This makes it easier for us to write internal extensions and the like.

“Additionally, we like that Microsoft is releasing monthly updates and continuing to improve performance. “

Read more: Microsoft Build 2019: Microsoft introduces new updates to the MS 365 platform with a focus on AI and developer productivity

“The Visual Studio Code team pays special attention to the issues that developers face”

Ajeet Dhaliwal is a software developer at Results. He explains that he used several different IDEs and editors, but came to Visual Studio Code after spending time using Node.js and React on Brackets.

“I have used Visual Studio Code almost exclusively for the past two years.

“In the years leading up to this change, the nature of the development work I did meant that I was largely limited to using specific IDEs like Visual Studio and Xcode. Then in 2014, I declared that I was going into Node.js and I was looking for a code editor that would be more suitable. I tried a few of them and ended up going with brackets.

“I used Brackets for a while, but I wasn’t always happy with it. The most annoying issue was the way the text rendered on my Mac.

“Over time I also started working on React and every time I revisited VSC the improvements were impressive, it seemed to me that the developers were paying close attention to the issues that the developers were facing, they were building features. which I never even thought I needed and the extensions added some very useful features for Node.js and React development work. Font rendering wasn’t a problem either, so it became an inevitable change.

“I have to change context regularly – I expect my brain to be the slowest element, not the IDE”

Kyle Balnave is a senior developer and team leader at High speed drive. Although he works with many editors and IDEs, he loves Visual Studio Code because it allows him to move incredibly quickly between different contexts. Simply put, it allows it to work faster than other IDEs.

“I have used several different editors over the years. They generally fall into two categories:
Monolithic (I can do whatever you want out of the box).
Modular (I do the basics but allow the addition of extensions to do the rest).

“The first are IDEs like Netbeans, IntelliJ and Visual Studio. In my experience, they are slow to load and need a more powerful development machine to stay responsive. They have a huge range of features, but in day to day development I just need it to be a smart code editor.

“These are IDEs like Eclipse, Visual Studio Code, Atom. They load quickly, respond quickly, and have a wide range of extensions that allow me to develop what I need. They sometimes lack functionality, but I generally find this infrequent.

“Why am I using VSCode? Because it doesn’t slow me down when I code. I have to change context regularly, so I expect my own brain to be the slowest element, not the IDE.

Learn how to develop with Node.js on Azure by downloading Learn Node.js with Azure for free, courtesy of Microsoft.

Leave A Reply

Your email address will not be published.