"This is the Monaco editor component from Erich Gamma's group out of Zurich. It was originally written in JavaScript but gradually rewritten in TypeScript. When Anders speaks about teams within Microsoft building large TypeScript systems, this is one he is talking about" as one comment mentioned on a related article "It's also used in VisualStudio and IE11's new F12 tools.": http://www.hanselman.com/blog/ARichNewJavaScriptCodeEditorSp...
"Code uses a newer, faster version of the same industrial-strength HTML-based editor that has powered the “Monaco” cloud editor, Internet Explorer's F12 Tools, and other projects.": https://code.visualstudio.com/Docs
It's based on Electron: http://electron.atom.io/
(look at the bottom of the page)
Look at the VSCode-linux-x64.zip in dir "\resources\app\server\" there is a "monaco.impl.js". It's the "monaco" editor component that comes from Switzerland that is also used in Visual Studio Online.
``` // Handle crashes reporter.start({ productName: 'Ticino', companyName: 'Microsoft', submitUrl: 'https://ticinocrashreporter.azurewebsites.net/crash', autoSubmit: true }); ```
But for those who care about their privacy, IMO its approaching the problem from the wrong angle if you're trying to get some developer to change their code to respect your privacy. Its their code. They can do what they want.
We as users should have protections from them attempting to submit information we don't want leaked. To me the solution is better perimeter monitoring and filtering.
While not practical in many situations I would highly recommend filtering all outbound traffic using a new firewall that supports such features (Sophos UTM for one, PfSense for another). Its the only way to know for sure those requests don't get out even when there is a disable option.
Edit: there is only a small "preview" symbol on the top left, beside that no text or screenshot mentions it: https://code.visualstudio.com/