


VS Code’s interface also includes another toolbar on the far left with buttons to change your view. The default view will show you your folders and files in the left column with the actual coding workspace in the large column on the right. The interface for VS Code will be familiar to you if you’ve used a coding editor before. The Quick Setup will guide you through picking a theme, adding coding languages and other extensions, turning on settings sync so that your settings can be synced across devices, and finally, opening a project to start work. VSCodium exists to make it easier to get the latest version of MIT-licensed VS Code.The VS Code Quick Setup guide (Image credit: Microsoft) Interface and in useĪ good place to start to get familiar with what Microsoft VS Code offers is the Getting Started Quick Setup, which can be accessed from the Help menu. If you want to build from source yourself, head over to Microsoft’s vscode repo and follow their instructions. These binaries are licensed under the MIT license. This project includes special build scripts that clone Microsoft’s vscode repo, run the build commands, and upload the resulting binaries for you to GitHub releases. The VSCodium project exists so that you don’t have to download+build from source. Therefore, you generate a “clean” build, without the Microsoft customizations, which is by default licensed under the MIT license When you clone and build from the vscode repo, none of these endpoints are configured in the default product.json. We clone the vscode repository, we lay down a customized product.json that has Microsoft specific functionality (telemetry, gallery, logo, etc.), and then produce a build that we release under our license. When we build Visual Studio Code, we do exactly this. According to this comment from a Visual Studio Code maintainer: Microsoft’s vscode source code is open source (MIT-licensed), but the product available for download (Visual Studio Code) is licensed under this not-FLOSS license and contains telemetry/tracking.
