View Single Post
Posts: 1,418 | Thanked: 1,541 times | Joined on Feb 2008
#12
Originally Posted by Bundyo View Post
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.
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.
 

The Following User Says Thank You to fms For This Useful Post: