I only recommend Chrome because it auto-updates. If one of my users starts using Chrome, I always know they'll have the latest and greatest. That's not yet the case with FF, but I'll recommend FF again as soon as the auto-updates land.
I only recommend Chrome because it auto-updates. If one of my users starts using Chrome, I always know they'll have the latest and greatest. That's not yet the case with FF, but I'll recommend FF again as soon as the auto-updates land.
As a web developer, I'm fed up of the moving targets and unreliability. When Firefox pushes an update to everyone and breaks something fundamental, it's not the Firefox support desk that gets complained at when the web apps stop working.
As a user, I see little real advantage from the breakneck pace of development anyway. Inevitably only a few sites use bleeding edge features within weeks of their appearance, and most of them seem to be web design/web development blogs showing off about bleeding edge features that might one day be useful to real web sites.
Moving to silent updates, as done by Chrome, might reduce the hassle, but then we'll also see endless minor UI tweaks happening at apparently random times like Chrome, which is really annoying in itself. And of course if a major bug gets pushed out and breaks a site I care about as a visitor, it's just as annoying whether I manually updated (not that there's much choice if security patches stop for anything more than five minutes old) or it happened silently in the background.
I never recommend Chrome or Firefox with the auto-updates. In fact, we explicitly don't provide customer support for them any more on several projects I work with, that conclusion being reached independently by several different development teams after experiencing all-too-similar problems. If anyone asks, I think the official recommendation in most cases is currently IE9.
That said, it's not just auto-update that makes Chrome more attractive. The omnibox, polarizing though it may be, sets Chrome apart from every other browser as far as U[I|X] goes. Oddly enough, that one feature alone is enough to make it my default browser. Were FF as fast as Chrome, I'd still use the latter because I just like using it more. Chrome's sandboxing, V8, and other intelligent features are just icing on the cake.
This, ultimately, confuses me more than anything about the other browser vendors' reaction to Chrome. They've copied or are copying just about everything about it: short release cycles, better JS engines, sandboxing... but not the one definitive UI feature that has made it so attractive to so many people. This surprises me. I would have though Apple, at least, with its commitment to minimalistic UIs, would have been quick to hop on that train, but no dice.
Personally, I just use vimperator (the clones of which on Chrome are…abysmal?) so I can o[pen]/t[abopen] and then type a search term (w/ customizable engine) or a URL.
…
Memorywise, the recent FFs are much better. Usually problems are caused by extensions.
Chrome, on the other hand, only exposes non-Google search engines through the search engine keyword thingy, which means a user has to actually type "en.wikipedia.org widgets" into the omnibox. Sure, tab-completion will do half the work, but the user still has to remember to start typing "en." rather than, say, "wikipedia".
I know that Chrome (and, indeed, Firefox) allow you to edit those search engine keywords, but that is power-user territory, and power-users can edit their Firefox UI as well. http://i.imgur.com/mS5Ot.png
The reason to keep the search field is people use it I guess. And there would be some confusion once removed.
Typing it into the Awesomebar will do an "I feel lucky" search.
For firefox, I use the https://addons.mozilla.org/en-US/firefox/addon/omnibar/ addon, it works quite well for me.
Now if only I could find a way to get firefox tabs into the title bar...