The biggest complaint about Chrome is the absence of an extension framework, something that made Firefox such a beloved browser. We already know Google is working on such a framework, but when is it coming? "We're working on that. As we said in the blog this is coming this year and it's certainly something that you want." Bak explains, "But when you are working on a new project it's important to focus on the basics, like our UI for instance, and I think other things come later and that's what we're doing."
I'm personally not very interested in an extension framework, mostly because, well, I don't use any extensions; I do use Flashblock on Firefox on Linux, but that's only because Flash has a tendency to crash, bringing down Firefox as a whole. Thanks to Chrome being modern and having a multi-process design, there's no need for such an extension. I just kill a crashed tab, and move on.
Still, it is obvious that it is a much-requested feature, but I do hope (in vain, I know) they release a build of Chrome without all that user-requested stuff, so I can continue to use Chrome for the same reason I'm using it now: no-nonsense, to-the-point browsing. I don't need my browser to make me coffee while gently rocking me back and forth - I need it to show web pages.