The really nice feature I think is that each individual tab in Chrome runs as its own separate PID. Maybe I'm out of touch and FF does this too now but AFAIK it's quite innovative. In theory, a nasty page wouldn't crash your whole browse, simply it's tab. Who knows.
in the old days, that was called forking a process, apache used to run that way. threading was invented with the intent of being more efficient and using less resources. this is really nothing new at all.
so, V8 does the JS VM, Webkit does the render engine and google takes all the credit for not adding a menubar and reintroducing fork();
when you consider that the really hard work was done by others (webkit is mostly apple engineers, and no osx version?) and the vastness of googles resources in both manpower and cash, then this duct taping of other people's work under their brand is not really as impressive as the firefox or ie efforts.
Google Chrome
in Everything Else
Posted
in the old days, that was called forking a process, apache used to run that way. threading was invented with the intent of being more efficient and using less resources. this is really nothing new at all.
so, V8 does the JS VM, Webkit does the render engine and google takes all the credit for not adding a menubar and reintroducing fork();
when you consider that the really hard work was done by others (webkit is mostly apple engineers, and no osx version?) and the vastness of googles resources in both manpower and cash, then this duct taping of other people's work under their brand is not really as impressive as the firefox or ie efforts.