Visual Studio Code License Agreement

code.visualstudio.com/License/ github.com/Microsoft/vscode github.com/Microsoft/vscode/blob/master/LICENSE.txt I thought it was common knowledge that the source code was open source, but the compiled binaries were not. This is not really new to most people. This is a kind of questionable scenario. Simply put, VSCode`s source code is open source, but the compiled binaries provided by Microsoft are not. So if you want a true open source edition, you can compile the source code yourself. Or you can use a community-compiled distribution such as vscodium. The only bad thing is that they have final control over the project, so if the community wants to add a feature that isn`t in their best interest, they can be a significant PR hurdle. Conversely, if there`s a feature they like, they`ll add it, whether the community likes it or not. Just like noting that even Chromium still contains proprietary code, you`ll need unrecognized chrome for this. Okay, Julian Assange, create and create your own code editor. Code and telemetry information are not secret, hidden, closed source, proprietary. You can view the telemetry code in the repository and view the telemetry information sent by setting the log level to tracked (F1 >set the developer`s log level >…) and then navigating to Protocol (Telemetry) in the Drop-down list in the Output panel. It`s even worse for Android.

The project and the base code are open, android OS is not. However, if you try to compile the operating system itself, you cannot because there are strict dependencies on Google services, without which the operating system will not work. And these services are licensed. There are a few open source alternatives like gapps, but lately Google wants you to get a certification key from them if you want to use these alternatives on real hardware. Similar to how Microsoft wants to provide UEFI keys for Linux distributions. Although I come across such a license for the first time, I am sure that I have neglected many of these licenses and would like to know more about the others. This section should be deleted or amended. The whole thing is based on the fact that the author has a misunderstanding about the difference between binaries and code with 2 different licenses.

There is a version of vscode that runs on a server, for those looking for an alternative. I share my code under the ISC license. I use OpenBSD. I pay money to server companies to use their hardware. You win. I have a secure server. I want this to continue. So it`s in my best interest to contribute money or diffs to OpenBSD.

You win. I win. Microsoft Windows 10 is a closed source and has a mountain of problems that their employees can`t seem to solve. This looks like a financial loss from the closed source. Play both ways. It`s so anti-thesis to recent news and announcements that you hear about Micrsoft`s commitment to open source, but skeptics have always been suspicious. And after reading the license, I`m too skeptical. Although it is very difficult to find a very good alternative to VSCode, and in the near future I will use VSCode by constraint of my own free will, I will definitely stop recommending VSCode as the IDE of choice. A code editor that provides IntelliSense, built-in Git, debugging capabilities and many improvements to add functionality. Microsoft provides two licenses: open source and commercial. I don`t see the problem with that. I switched to vscodium after learning about the closed telemetry source code that Microsoft adds to vscode.

So the vscode source is updated with the bug fixes found by telemetry in vscode, and then vscodium gets the code fixes? It`s great as a stowaway approach, but if the telemetry and corrections weren`t there, Vscodium would suffer. So it`s time for everyone to ask themselves if VSCode is really as open source as Eclipse or pure FOSS IDEs or publishers that are owned and powered by the community. This is not only the problem of VSCode, but also the problem of many other open source « community » editions of expiatory products, where while most of the basic features are developed by the company, the ecosystem built with others is threatened by the restrictive license. But the particular problem I have with VScode is that its source code and binaries are dual-licensed and completely opposite. The MIT license is valid for the source. For the binary version, they can distribute VS with all the « bonus » features and their own license. The first VSCode source code is released under the MIT license, but if you look at the chips in the Visual Studio Code product license, they are a complete antithesis of the MIT license with which it is distributed. Now let`s look at the MIT license. Microsoft has code in its version that they don`t want you to unpack.

There you go. Hence the license agreement. Nothing at all, telemetry to guide a product is great. Why is it a closed source? And what else is in the code? What prevents the addition of other « actions » to this telemetry code base? Just FUD? Times are changing. SCO tried to destroy Linux to advance their software. Oracle releases the JVM under a much more restrictive commercial license. Red Hat could turn into a patent troll. Richard Stallman is invited to retire from the GNU Foundation. Linus Torvalds can be incredibly rude and sensitive to his own contributors.

reverse engineer, decompile, disassemble or otherwise attempt to derive the source code of the Software, except and only to the extent required by the terms of the third-party license agreement for the use of certain open source components that may be included in the Software; Those who are not interested or do not understand the problem of dual licensing and its implications may ignore my message. But those who do should explore vscodium with a clear licensing provision. As with Stack Exchange, one user commented: Ugh. Yes. This could be a very good time to fork every piece of Google code that is still open and run away with it. Is the Go compiler still OSS? This license applies to the Visual Studio Code product. The source code for Visual Studio Code is available from github.com/Microsoft/vscode under the MIT license agreement to github.com/Microsoft/vscode/blob/master/LICENSE.txt. You can find more information about licensing in our FAQ under code.visualstudio.com/docs/supporting/faq.

Subject to clause (ii) above, Microsoft will only be liable for slight negligence if Microsoft breaches those important contractual obligations, the performance of which facilitates the proper performance of this Agreement, the breach of which would compromise the subject matter of this Agreement, and on which a party can constantly rely (referred to as « Cardinal Obligations »). In other cases of slight negligence, Microsoft will not be liable for slight negligence. You can get a version of the open source with vscode licensed here These license terms are an agreement between you and Microsoft Corporation (or depending on where you live, one of its affiliates). They apply to the above software. The Terms also apply to all Microsoft services or Software updates, unless they have other terms. There are also other things like copyrighted icons/logos, marketplace/debugging/update code, but that`s not worthy of a conspiracy, is it? It`s no different from Chrome and Chromium. The product that most people download and install has additional proprietary features and code, but is based on a truly open source code base. If you have a problem with this, you should also have a problem with Chrome. So if you read between the finest lines while the source code is open source and free to modify, the binaries with which it was created are not completely FOSS.

It has restrictive conditions that I assume Microsoft, as an enterprise software company, must follow and is subject to U.S. cyber laws and export restrictions. .