He's done a lot of work to make it as straightforward as possible. If you want to try it out for yourself, you can follow the instructions he has laid out. I've maintained the project for a few years now and it has expanded from providing binaries for Pi to providing support and tools to get VS Code running on low-end ARM devices that might not otherwise support it like Chromebooks (which make up about 60% of the devices in schools now). Jay Rodgers released an open-source project that performs nightly builds of VS Code for Raspberry Pi and Chromebooks. Unofficial community builds for Raspberry Pi and Chromebooks Linux (Red Hat): Red Hat Enterprise Linux 7, CentOS 7, Fedora 23.

Linux (Debian): Ubuntu Desktop 14.04, Debian 7.VS Code has been tested on the following Operating Systems: Minimum hardware and software requirementsīefore we get into extensions, let's talk briefly about what the minimum requirements for running VS Code are.Ī computer bought in the last few years with modest specifications should be able to run VS Code without any issues. Then I will outline how you can audit the performance of your existing extension suite, and give some general performance tips. I will also grade the performance of some popular extensions. In this article, I will explain the factors that affect the performance of an extension. It has a tight set of core features, and you can add extra features through extensions.īut performance will inevitably be affected as your collection of extensions grows.ĭo you evaluate the performance of an extension before installing it? What do you do if the startup of VS Code grows? From the absence of people writing about this topic, I guess people don't know. Visual Studio Code (VS Code) is designed to be lightweight.

Visual studio reset intellisense