Linked by Thom Holwerda on Fri 5th Sep 2008 21:57 UTC, submitted by rkalla
Chrome's process model is extremely sophisticated. The default behavior has been examined before, but you can configure Chrome to manage processes differently: one process per web site, or one process per group of connected tabs, or one process for everything. Marc explains how this all works in Google's new browser. Update: 'Read more' fixed - made a reading comprehension boo-boo there.
Thread beginning with comment 329396
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:
2006-06-03
Sure, if you go along with the one user fits all approach, then yes, the developers should sit down 'the user' and test him till he bleeds to find out which method is best.
Being rather subtler than that, however, they have tested, and provided, an optimal default that 99% of users are expected to be satisfied with. People with non-standard hardware or software requirements however, can, with a little research, find out how to make chrome suit their particular needs more often.
This sort of customisability is applauded in most Open Source software, why not this piece?