Exciting news for Android. It’s always been a wonder why the stock Browser wasn’t Chrome, and now it is. And it really rocks. The tab interface is fun to use.
However, since it uses an updated version of the webkit rendering engine, it should need to load that library upon initialization. The standard engine is always in memory, something that’s held back Firefox for Android. Yet, Chrome doesn’t seem to suffer from this.
Perhaps the mobile Firefox engineers already know, but I can think of 3 possibilities:
There’s a way to keep the new libraries in memory.
There’s a way to replace the default engine
Or they just handle the loading in a better way.
Whichever it is, hopefully mobile Firefox can find a way to improve their loading to be close to equivalent to Chrome’s loading.