3 ms·

I think I might be missing the sliminess here. MS invested time and money to build software and is offering it for free. As part of that offering they are bundl

I think I might be missing the sliminess here. MS invested time and money to build software and is offering it for free. As part of that offering they are bundling up the software to the point that you can just download it and run it. In exchange for this they want to be able to collect usage statistics so they know how their software is being used. They are also giving you the option to download the software from source and build it yourself if you don't want them to see how you are using the software. This all seems pretty fair to me.

SmellyGeekBoy 8y ago
Agreed. It doesn't seem any different to what, for example, Red Hat do with RHEL (which I also don't see the problem with).
- sam0x17 8y ago
  Microsoft has a much darker past to come back from with this, so the stakes and expectations are much higher and community willingness to forgive much lower
sam0x17 8y ago
The telemetry code (spyware) that is clearly in the binaries but missing from the MIT-licensed source code (people have already determined that the binaries don't match a build of the source code).
- bpicolo 8y ago
  The telemetry usage is directly in the MIT source: https://github.com/Microsoft/vscode/blob/f05063d13da8c6112ed439e3a36836960ad005cd/extensions/typescript-language-features/src/utils/telemetry.ts https://github.com/Microsoft/vscode/blob/f05063d13da8c6112ed... The telemetry extension is open source too: https://github.com/Microsoft/vscode-extension-telemetry https://github.com/Microsoft/vscode-extension-telemetry And you can unpack the source for the distributed electron bundle yourself: https://medium.com/how-to-electron/how-to-get-source-code-of-any-electron-application-cbb5c7726c37 https://medium.com/how-to-electron/how-to-get-source-code-of...
  - sam0x17 8y ago
    Then there is literally no reason for the license discrepancy
    - jklein11 8y ago
      There is certainly A reason for the license discrepancy. It just may or may not be a good one.

SmellyGeekBoy 8y ago

Agreed. It doesn't seem any different to what, for example, Red Hat do with RHEL (which I also don't see the problem with).

sam0x17 8y ago
Microsoft has a much darker past to come back from with this, so the stakes and expectations are much higher and community willingness to forgive much lower

sam0x17 8y ago

The telemetry code (spyware) that is clearly in the binaries but missing from the MIT-licensed source code (people have already determined that the binaries don't match a build of the source code).

bpicolo 8y ago
The telemetry usage is directly in the MIT source: https://github.com/Microsoft/vscode/blob/f05063d13da8c6112ed439e3a36836960ad005cd/extensions/typescript-language-features/src/utils/telemetry.ts https://github.com/Microsoft/vscode/blob/f05063d13da8c6112ed... The telemetry extension is open source too: https://github.com/Microsoft/vscode-extension-telemetry https://github.com/Microsoft/vscode-extension-telemetry And you can unpack the source for the distributed electron bundle yourself: https://medium.com/how-to-electron/how-to-get-source-code-of-any-electron-application-cbb5c7726c37 https://medium.com/how-to-electron/how-to-get-source-code-of...
- sam0x17 8y ago
  Then there is literally no reason for the license discrepancy
  - jklein11 8y ago
    There is certainly A reason for the license discrepancy. It just may or may not be a good one.