You Think the Visual Studio Code Binary You Use Is Open Source? Think Again
1–10 of 35 posts
Re: You Think the Visual Studio Code Binary You Use Is Open Source? Think Again
#2Is there any technical evidence that Microsoft is doing something suspicious with the binaries? Differing hashes? Weird network traffic? Binary de-compilation? Its not hard to find evidence if you've got a hunch, instead of publishing a fear piece like this.
Re: You Think the Visual Studio Code Binary You Use Is Open Source? Think Again
#3Is there any technical evidence that Microsoft is doing something suspicious with the binaries? Differing hashes? Weird network traffic? Binary de-compilation? Its not hard to find evidence if you've got a hunch, instead of publishing a fear piece like this.
It is a fear piece, but the premise that the binary is not MIT-licensed is true. This is the same for the dotNET core binaries, they don't have the same license as the source either. Now I think of it, this probably applies to most open-source libraries including ASP.NET MVC. Perhaps because they use hardware-based signing of the binary?
Re: You Think the Visual Studio Code Binary You Use Is Open Source? Think Again
#4Is there any technical evidence that Microsoft is doing something suspicious with the binaries? Differing hashes? Weird network traffic? Binary de-compilation? Its not hard to find evidence if you've got a hunch, instead of publishing a fear piece like this.
The license forbids you to reverse-engineer, so how would you find out without breaking the license?
Re: You Think the Visual Studio Code Binary You Use Is Open Source? Think Again
#5Wrong title. Article says "free software" which makes much more sense than "open source" in title. On HN you should know the difference.
Re: You Think the Visual Studio Code Binary You Use Is Open Source? Think Again
#6This has been known for nearly two years now[1], and was talked about here a few months ago[2].
VSCode also downloads code from MicroSoft servers during the build process and won't build without an Internet connection. I'm pretty sure someone had forked VSCode like ungoogled-chromium but I can't find the repository.
[1] https://github.com/Microsoft/vscode/issues/17996 [2] https://news.ycombinator.com/item?id=17346492
Re: You Think the Visual Studio Code Binary You Use Is Open Source? Think Again
#7Wrong title. Article says "free software" which makes much more sense than "open source" in title. On HN you should know the difference.
On HN people also think real time software can be written in node.js ;)
Most smart people on HN are silent mostly since it's been taken over by the Javascript horde.
Re: You Think the Visual Studio Code Binary You Use Is Open Source? Think Again
#8Is there any technical evidence that Microsoft is doing something suspicious with the binaries? Differing hashes? Weird network traffic? Binary de-compilation? Its not hard to find evidence if you've got a hunch, instead of publishing a fear piece like this.
It is a fear piece, but the premise that the binary is not MIT-licensed is true. This is the same for the dotNET core binaries, they don't have the same license as the source either. Now I think of it, this probably applies to most open-source libraries including ASP.NET MVC. Perhaps because they use hardware-based signing of the binary?
>It is a fear piece,
Why, you are even forbidden to reverse engineer or hack the binary so it is the total opposite of free software.
Any idea why would they put this limitations on the binaries? What does MS gains for this ?
Re: You Think the Visual Studio Code Binary You Use Is Open Source? Think Again
#9Wrong title. Article says "free software" which makes much more sense than "open source" in title. On HN you should know the difference.
The software is "open source" not just "free software". The binary itself is not "open source".
Re: You Think the Visual Studio Code Binary You Use Is Open Source? Think Again
#10Earlier quoted context omitted.
It is a fear piece, but the premise that the binary is not MIT-licensed is true. This is the same for the dotNET core binaries, they don't have the same license as the source either. Now I think of it, this probably applies to most open-source libraries including ASP.NET MVC. Perhaps because they use hardware-based signing of the binary?
>It is a fear piece, Why, you are even forbidden to reverse engineer or hack the binary so it is the total opposite of free software. Any idea why would they put this limitations on the binaries? What does MS gains for this ?
[deleted]