> How does this “kill the product for healthcare, finance and defence sectors”? This is part of the SDK tooling, it should not installed or run in the deployment evnvironment.
This will also be installed in places like the build server that may have extra permissions into the production environment. Often the firewall between production and development won't be as great as you think and all software has to be compliant because the developers will be dealing with real private data.
> If teletmetry is bad, running “dotnet restore” to download code from the internet is worse
"dotnet restore" could be hitting a local repository only, which is much more common in these environments.
> If having telemetry in the development environment is bad too, then so was the “Visual Studio Customer Experience Program”.
Typically it would be disabled, but things slip through the cracks, no matter how many precautions there are, which is why off by default is important.
Aside from that, it kills trust. The developers don't even understand that this is a privacy violation and refuse to fix it, so when the next thing on the slippery slope comes along I don't expect them to appreciate the ramifications of it. Will compiler error codes be considered telemetry? How about exceptions? How about code metrics? I can't trust the dotnetcore developers to respect privacy.