> Transparent updates, especially when they're nigh-totally transparent, are in an entirely different world than "do you want to update yes/no/cancel" Transpar

> Transparent updates, especially when they're nigh-totally transparent, are in an entirely different world than "do you want to update yes/no/cancel" Transparent updates are great, until something goes wrong. What happens if someone manages to hijack the DNS entry to make 50 million Chrome installations download an update from a poisoned well? Or Google's quality control misses something and pushes out a buggy update that breaks Chrome's ability to reconnect and obtain a fix for that update? (This has already happened to companies the size of Skype and McAfee.) Or an update simply introduces a behavior that users don't want, like Microsoft using Windows Update to inflict WGA everywhere. The net benefit of transparent updates is still probably greater than explicit updates, but both ways have costs and we shouldn't pretend that either is zero.