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.
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.
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...
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.