On Fri, Sep 25, 2009 at 10:24 AM, Darin Fisher <da...@chromium.org> wrote:
> On Fri, Sep 25, 2009 at 10:22 AM, Nico Weber <tha...@chromium.org> wrote:
>>
>> >> At times, we seem to forget the impact of our silent updates. They are
>> >> great for bug/security fixes, but when we do roll out something like
>> >> NNTP,
>> >> it can lead to a 'WTF' moment. For future changes like this, it might
>> >> make
>> >> sense to put in messaging for the upgrade so the users get lead through
>> >> the
>> >> transition instead of their routine suddenly changing on them.
>> >
>> > All software, and all browsers, change their UI and capabilities as they
>> > release new versions. Look at how Firefox 1.0, 2.0, 3.0, and 3.5 all
>> > had
>> > different main window themes (and not just cosmetically; they moved
>> > pieces
>> > around and changed the UX). It's not like there was a "--use_2_0_theme"
>> > switch when 3.0 released.
>> > Users complain about anything that changes. This is why user complaints
>> > should be an input, but not a hugely-weighted one.
>>
>> FWIW, Firefox uses can choose not to update to a new version if they
>> don't like the new UI though ( and some people mention this explicitly
>> as a reason for not updating:
>>
>> http://blog.mozilla.com/metrics/2009/08/21/why-people-dont-upgrade-their-browser-part-i/
>> ).
>
> It's also not something Mozilla supports. Eventually, they stop offering
> security updates
> for old versions.
Sure, and I guess most people update eventually, but they can go
through their five stages of grief at their own speed. With
autoupdate, they get the new UI while they might still be in the
Denial or Anger stages :-)
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
