Google Chrome 14 seems to be a severe resource hog. Each time I use it, the rest of the system seems to grind to a halt. I was never convinced with the view that using independent processes instead of threads was a better idea to keep the browser components running smoothly. It seemed regressive then. It seems regressive now more than ever.
Firefox, on the other hand, seems to have put its reputation as a resource hog well behind it. The latest version seems to be leaner and meaner than ever. Best of all, they have stuck to their guns and continue to rely of threads instead of processes. The memory load has been most impressive and a recent browser comparison put Firefox well ahead of all its competitors.
Perhaps it’s time Google learned a thing or two from its free-spirited cousin!