3 ms·
Wait, so running and modifying stuff on all users' computers is good, but a random sample isn't? That's what A/B testing deals with. The discussion isn't "modi
by scarejunba 8y ago
Wait, so running and modifying stuff on all users' computers is good, but a random sample isn't? That's what A/B testing deals with.
The discussion isn't "modify stuff" vs. "don't modify stuff". The discussion is "some users" vs. "all users".
And obviously if you have an auto-update mechanism you're modifying stuff on the user's computer. Chrome updates are near invisible on modern machines. That's a good thing. It keeps the browser evergreen and protects users. If everything were opt-in because "Google shouldn't modify stuff on my computer" that would be an absolute disaster for everyone. No way.
- Crinus 8y agoThis is a technicality, users do not care about technicalities, they have their own expectations and if you are on -say- a stable branch with autoupdates enabled your expectation is that you'll get the latest version that everyone else is using. A/B testing through that branch breaks that expectation (and no, mentioning it somewhere hidden in some EULA or equally obfuscated place does not mean people will not have the expectation - hell, even mentioning it right below the download wont make a difference).