“ Google also say they’re using a “multi-process design” which they say means “a bit more memory up front” but over time also “less memory bloat.” When web pages or plug-ins do use a lot of memory, you can spot them in Chrome’s task manager, “placing blame where blame belongs.”
[…]
By implementing this feature a browser is completely deflecting all memory or performance criticism off to individual site owners (“Yikes, my browser is using 300MB of memory! Actually it’s just youtube.com consuming 290MB of it, they should fix their web site!”). This is going to be a monumental shift in the responsibilities of web developers - and one that will serve the web better, as a whole.
[…]
By implementing this feature a browser is completely deflecting all memory or performance criticism off to individual site owners (“Yikes, my browser is using 300MB of memory! Actually it’s just youtube.com consuming 290MB of it, they should fix their web site!”). This is going to be a monumental shift in the responsibilities of web developers - and one that will serve the web better, as a whole.
