Okay, FF3.1 JS is another 7x times faster than 3.0 and is already stable-ish, CSS has almost full 3.0 support and 85/100 on ACID3, so when the time comes Nokia to update MicroB, there are options available... Let's hope that's before FF4.0 comes out.

Now that i'm writing something which has to look good in MicroB, i'm seeing where the decision to adopt an alpha engine pays off.

None of these extensions will fix the subject of this thread though. The problem is that at some point Nokia decided to put the whole FF-derived browser into a daemon, difficult to kill if it fails and using gobs of shared memory for communicating with clients. Given the sheer size of the engine and its complexity (read: propensity to failure), making it resident does not seem to be such a good idea, especially if all it does is shaving 2 seconds off the startup time.

I would say, make it optional, the same way Python Launcher works.

JS is actually the biggest problem in microb and the N8xx generally. There are tons of sites which demand a quadcore-2G processor to be run efficiently - and that's where our tiny N8xx will forever fail.

Normally I browse with JS switched off, a much faster browsing experience.

And yep, ad-blocking with CSS is the way to go, as GA has mentioned.