The source code has been released by Microsoft under the open-source MIT license, but the product available for download (Visual Studio Code) is licensed under this proprietary license. Sure there's also the JetBrains product suite, Emacs, Neovim, XCode and Visual Studio, but VSCode is likely installed on your computer right now.

Visual Studio Code was released 7 years ago and is fast becoming the de facto standard editor that people use when doing software development. Visual studio code is now seven years old Yup! And that’s by design 🙂- Phillip Carter May 18, 2022īy the end of this blog post, I hope more folks understand that by using anything other than the official distribution of Visual Studio Code provided by Microsoft (or GitHub via Codespaces) that it is easy to expose yourself or your company to legal risks similar to incorrectly using Docker Desktop or the Oracle JDK. In this blog post, we explore the ecosystem of open-source forks, revisit the story so far with how Microsoft has been transforming from products to services, go deep into why the Visual Studio Code ecosystem is designed to fracture, and the legal implications of this design then discuss future problems faced by the software development ecosystem if our industry continues as-is on the current path. Whilst Visual Studio Code is ' open-source' (as per the OSD) the value-add which transforms the editor into anything of value ('what people actually refer to when they talk about using VSCode') is far from open and full of intentionally designed minefields that often makes using Visual Studio Code in any other way than what Microsoft desires legally risky.

Now that I'm no longer an employee at Gitpod, I'm finally able to author a blog post freely about something that has been troubling me for quite some time. A couple of moments ago, I finished reading the article by Rob O'Leary about the pervasive data collection done by Visual Studio Code.

Review visual studio code linux c++