So the Microsoft software license is definitely not a free software license if you haven`t been convinced by the clever trick of dual licensing source code and binary. So if you read between the thinner lines, while the source code is open source and free for editing, the binaries it`s created with aren`t entirely FOSS. It has restrictive conditions that I assume Microsoft must follow as an enterprise software company and is subject to U.S. cyber laws and export restrictions. Therefore, people who use vsCode at the end of the day are subject to all Microsoft licensing restrictions. This may very well apply to community contributors who create the rich set of community plugins that make VSCode so appealing. It`s even the worst for Android. The project and base code are open, Android OS is not. But if you try to compile the operating system yourself, you can not do it, because there are strong dependencies on Google services without which the operating system is not functional. 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. Much like Microsoft wants to provide UEFI keys for Linux distributions.
However, I still use VSCode, but I run vscode in a prison without internet access. While I agree that it`s not clear enough that the binary you download also contains proprietary code, I see no problem distributing the binary under a license other than the source code if the license doesn`t require it. And even if that`s the case, as is the case with GPL licenses, you may only want to make parts of your product open source (for commercial, legal, or other reasons). Quake`s source code, for example, was released under the GPL, while its assets were still proprietary. My opinion is that if this is the case, it should be clearly indicated by having a community version and a paid version, or simply by calling the products differently, as Google does with Chromium and Chrome. Although VSCodium removes this code, it is also not hidden from the public or “added” to the official version of MS. What is excluded from the MIT license filing and added to the MS-licensed version are the URLs and keys used by the telemetry code. Excluding private and other keys from a Git repository is common practice, right? To repeat, you do not add telemetry code to the MS version, but exclude any drop telemetry keys required for this feature.
(Of course, those who are biased against MS will point out that there is probably code that implements telemetry in the market/debugging/etc. code that comes with the official version – but that`s beside the point.) This license applies to the Visual Studio Code product. The source code for Visual Studio Code is available under 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. This license applies to the Visual Studio Code product. The source code is available under the MIT License Agreement. When we create Visual Studio Code, that`s exactly what we do. We clon the vscode repository, define a custom product.json that has Microsoft-specific features (telemetry, gallery, logo, etc.), and then create a version that we release under our license. .