3 ms·
> But I also need to not be fucked with when I'm trying to work. But that's true of shipping any bug and isn't guaranteed to happen with a field trial any more
by magicalist 9y ago
> But I also need to not be fucked with when I'm trying to work.
But that's true of shipping any bug and isn't guaranteed to happen with a field trial any more than any new feature.
(and the OP doesn't seem to establish that it has anything to do with the field trial, just that the processes were run with that option? Admittedly I don't know how they actually work :)
- csydas 9y agoI think the point is more about intentional performance degredation versus unintentional; it makes sense that you can't ship a 100% bug proof piece of relatively complex software, and some has to be patched out later, but such performance degredation or workflow interruptions can be planned for. But to intentionally enable an function which knowingly degrades performance or impedes workflows just for the sake of testing without the consent of the user is a bit rude. To repeat the author and other comments, if it were a beta-channel or test build where it was clear this was part of the intended functionality of the build, I don't think we'd be having this discussion.
- jhasse 9y ago> But that's true of shipping any bug The difference is though, that I can choose the time I update Chromium myself.