This is something I hadn't noticed in the earlier postings about this browser: "By keeping each tab in an isolated "sandbox", we were able to prevent one tab f

This is something I hadn't noticed in the earlier postings about this browser: "By keeping each tab in an isolated "sandbox", we were able to prevent one tab from crashing another and provide improved protection from rogue sites." While the other features of the browser are hard to judge without active usage, this one is huge. Firefox, for all its virtues, is still too much like early 90's operating systems -- not enough separation between processes (tabs). In fact, since the browser is now the de-facto OS for a large variety of applications, it makes sense for browser writers to consciously design it as such. This means not repeating mistakes made in the OS world (mistakes such as not running processes in their own protected memory space, or using cooperative multitasking instead of preemptive, etc.) Also, while firebug plays its role as gdb-for-the-web admirably, we're still in need of some os-monitoring tools: top, free, and some tools to more closely look at memory usage. With the increasing number of high-quality browsers, I'm hoping at least some of them will make this realization and push in the right direction.