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.
Permalink for comment 329403
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-07-06
I voted you up because I think you bring up a good point, but I disagree. It could cut either way. I agree with you that more defects in the code will be manifest by giving users more flexibility with how they use the program, but the argument could also be made that forcing the developers to accommodate a larger variety of usage scenarios would force the overall code quality to be higher to reach release quality.