Portál AbcLinuxu, 22. prosince 2025 14:27
apt hrabe na pana Hagaru!... You may notNajmä ten prvý bod je zaujímavý, kto sa pozrie na zdrojáky na githube porušuje licenciu! A keďže github patrí Mrkvosoftu, vedia kto tam lezie... Tak hurá inštalovať!
- reverse engineer, decompile or disassemble the software, or otherwise attempt to derive the source code for the software except and solely to the extent required by third party licensing terms governing use of certain open source components that may be included in the software;
- remove, minimize, block or modify any notices of Microsoft or its suppliers in the software;
- share, publish, rent or lease the software, or provide the software as a stand-alone offering for others to use.
We build on top of the vscode code base we just open sourced and we release it under a standard, pre-release Microsoft license. The cool thing about all of this is that you have the choice to use the Visual Studio Code branded product under our license or you can build a version of the tool straight from the vscode repository, under the MIT license. Here's how it works. When you build from the vscode repository, you can configure the resulting tool by customizing the product.json file. This file controls things like the Gallery endpoints, “Send-a-Smile” endpoints, telemetry endpoints, logos, names, and more. When we build Visual Studio Code, we do exactly this. 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 you clone and build from the vscode repo, none of these endpoints are configured in the default product.json. Therefore, you generate a "clean" build, without the Microsoft customizations, which is by default licensed under the MIT license (note, i made this commit to help make this more clear). I hope this helps explain why our Microsoft branded Visual Studio Code product has a custom product license while the vscode open source repository has an MIT license. Last, I apologize for the fact that the naming of “Visual Studio Code”, “VS Code” and the vscode repository are so similar, I think it contributed to the confusion.
>retard >slovákům ostuduTak určitě.
https://github.com/Microsoft/vscode/issues/60#issuecomment-161792005
Zjednodušene pre Slavka: ak si zbuildíš binárku sám, je pod MIT, pretože aj kód je pod MIT. Ak použiješ binarku zbuildenú microsoftom,potom platí proprietárna licencia.
Už se to tu řešilo minule. Jsou to špíny, nemá cenu se tím zabývat.
Pokud někdo tenhle software mermomocí potřebuje, tak existuje jakési vscodium (nezkoušel jsem), které jeho autoři čistí od MS věcí a telemetrie.
Viz ta předchozí diskuse odkazovaná výše:
V podstatě je mi jedno, pod jakou licencí šíří MS svůj software, pokud mne tím nepoškozuje. Jenže tímhle mne (resp. nás všechny) právě poškozuje – propagují to jako „ Free. Open source. Runs everywhere.“ a hned pod tím je tlačítko, kterým si člověk stáhne proprietární software.
Rekni nekomu na ostravsku nahlas ... a dostanes rucni skoleni.ostravsko je nějaká rezervace neandrtálců, nebo proč by se hned kvůli tomu mlátili?
Tiskni
Sdílej:
ISSN 1214-1267, (c) 1999-2007 Stickfish s.r.o.