> The hoopla with command line arguments should be enough to underline the fundamental problem with that approach. It's worthless in that assurances don't mean

> The hoopla with command line arguments should be enough to underline the fundamental problem with that approach. It's worthless in that assurances don't mean a thing, even if they are given with best intentions and to the best of their knowledge. In this case I could easily verify that their assurance was wrong (they even admitted in the github discussion that transmitting command line arguments violates their own privacy policy), but the deed would have been done. And for the rest: as I said, I'm all for telemetry. If it's clearly communicated and opt-in. Other tools do it (as mentioned in github, e.g. yeoman) and live well with it.