4 ms·

A nit to pick here: Google releases Chrome, not Chromium. We only provide Chromium as a source repository, not binaries. Other independent entities (such as Lin

A nit to pick here: Google releases Chrome, not Chromium. We only provide Chromium as a source repository, not binaries. Other independent entities (such as Linux distros) can provide releases of Chromium, but Google does not. That said, Google doesn't support previous releases for security reasons. We are constantly improving the security profile of Chrome, and hackers (both black hat and white hat) are constantly finding exploits in older versions. (The same is true for all the other major browsers on the market.) If you want to use Chrome on a previous/older release, please don't. If you want to use Chromium on a previous/older release, also please don't, but you can compile it yourself if you're so inclined. And for the most part, no, customers don't demand stable old releases of Chrome. They've learned how bad of a security and usability mistake that is from IE6, and they don't want to repeat past mistakes any more than we do.

dragonwriter 11y ago
> And for the most part, no, customers don't demand stable old releases of Chrome. They've learned how bad of a security and usability mistake that is from IE6, and they don't want to repeat past mistakes any more than we do. I suspect that there are lots of enterprise customers that haven't learned that (encountered it, but not learned it), but they probably aren't Chrome customers, since they are still using IE.
- bengoodger 11y ago
  While we acknowledge some people might think they want this feature, it's been something we've been unexcited about helping them with it for the reasons stated. Having the ability to quickly deploy security fixes is fundamental to Chrome's ethos. This is as close to a point of religion for the Chrome team as you can get.
  - tyingq 11y ago
    I suspect IT customers actually wanted something in between the two extremes. Your existing IT customers may feel okay about it now, but could change their minds if, for example, a fairly drastic UI change is pushed out.

dragonwriter 11y ago

> And for the most part, no, customers don't demand stable old releases of Chrome. They've learned how bad of a security and usability mistake that is from IE6, and they don't want to repeat past mistakes any more than we do. I suspect that there are lots of enterprise customers that haven't learned that (encountered it, but not learned it), but they probably aren't Chrome customers, since they are still using IE.

bengoodger 11y ago
While we acknowledge some people might think they want this feature, it's been something we've been unexcited about helping them with it for the reasons stated. Having the ability to quickly deploy security fixes is fundamental to Chrome's ethos. This is as close to a point of religion for the Chrome team as you can get.
- tyingq 11y ago
  I suspect IT customers actually wanted something in between the two extremes. Your existing IT customers may feel okay about it now, but could change their minds if, for example, a fairly drastic UI change is pushed out.