3 ms·
This argument is nonsense. Everywhere you have to remember to use the non tracking compiler and everywhere you have to remember to set the variable are at best
by sophacles 4y ago
This argument is nonsense. Everywhere you have to remember to use the non tracking compiler and everywhere you have to remember to set the variable are at best the exact same set. More likely it's actually more places that require remembering to set the variable since various build environments and tools tend to strip out variables in all sorts of places.
It also assumes setting the variable actually works - even without malicious intent, it's an approach that assumes there are never any bugs.
- growse 4y agoThe fork is created out of thin air, and maintained invisibly, for free?
- sophacles 4y agoWe'll have to see the implementation of course, but it shouldn't be a huge effort to replace the telemtry reporting function with `return success`.
- ModernMech 4y agoThe complexity of the patch isn't the issue, it's keeping up-to-date with the upstream code. This can be done but it requires constant work, discipline, and it probably would need funding. But the worst part is that it sends the message that we as a community will tolerate megacorps injecting telemetry tracking into our compilers, and our response will be not only to stay in their ecosystem, but to do extra work for them to keep us there. That's not the the message I want Google to hear; I want them to hear us tell them where they can take their telemetry and shove it. We do that with our feet.