3 ms·

Google Chrome has been using auto upgrades for years and I haven't heard any complains about that. I'd argue it's also a really important tool in a dev's toolki

• rossdavidh 6y ago
  I suppose it's because, while not every version is great, it hasn't (that I am aware of) totally broken Chrome for any significant chunk of their users. It may be that is due to a bigger budget for QA at Google, or perhaps the intrinsic challenge of the two tools, but for whatever reason it hasn't happened (that I know of). If it did, I think there would be plenty of squawking.
  • kps 6y ago
    Chrome does several things right. (Disclaimer: I used to work on ChromeOS/Chrome, but this is just my opinion (but you can have it if you want).) - A beta stream that's one release ahead, which tends to be selected by web developers and other whiny^H^H^H^H^H demanding users. - Gradual release of new versions, starting with something like 1% of users, then 10%, then 100%. - Significant changes are behind run-time flags (chrome://flags), and ship disabled by default. After one or often several releases, where it can be optionally enabled, it becomes enabled by default, with the ability to back out if something goes wrong. Finally, only once it's been successfully enabled for several releases, the flag and the old code can be removed. - Nobody minds if a feature doesn't make it in to a release; there'll be another one in month or two. There's no pressure to cram in something half-baked to meet a deadline.