3 ms·

The problem isn't about 'rapid release cycles', but about the UX design of the update process. Even before the rapid release cycles, Firefox would check for add

by Geee 14y ago

The problem isn't about 'rapid release cycles', but about the UX design of the update process. Even before the rapid release cycles, Firefox would check for add-on updates every time it was started. Chrome's update mechanism is completely seamless and invisible and requires zero user attention.

breadbox 14y ago
Which, ironically, is almost as bad, when you suddenly realize that you basically let Chrome change the UI, and there's no way to return to the UI you once knew.
- overcyn 14y ago
  Is it almost as bad though if people are moving from firefox to chrome?
- uxp 14y ago
  Except that Chrome has never really changed it's UI. The presentation at the end of Google's 2012 IO Day 2 keynote actually timelapses through the UI. The only change is the removal of the home button outside of general micro-tweaks. http://www.youtube.com/watch?v=tPtJd6AzU8c&feature=player_detailpage#t=3579s http://www.youtube.com/watch?v=tPtJd6AzU8c&feature=playe...
  - grabastic 14y ago
    Although... to my great frustration, Chrome has made pretty big changes to their preferences pages over time.
  - pkamb 14y ago
    The only one that's really bothered me is the removal of the "Go" button on the right side of the URL bar. Still miss it.