I somehow doubt that the Google browser concept would work well on limited platforms like the NITs. The strength of Google's concept is that every tab is isolated from the rest by running as an own process. On the NIT, however, you don't have that much RAM available, so that it's better to have all tabs running in once process sharing as much resources as possible. That's why Nokia introduced "browserd". Also, from what I have seen, the Gecko engine is currently a bit faster than Webkit (but let's see what speed improvements Google will achieve with Webkit). But what's definitely interesting for the NITs is Google's new approach of a JavaScript VM with JIT and proper garbage collection. Since it's opensource, I'm sure it won't take long until Firefox gets the same.