Linked by David Adams on Tue 23rd Dec 2008 16:40 UTC, submitted by judgen
Thread beginning with comment 341274
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.
RE[3]: Reinventing the wheel :(
by Delgarde on Tue 23rd Dec 2008 22:50
in reply to "RE[2]: Reinventing the wheel :("
Do you know that IE8 is doing same thing that Chrome did. I mean creating a new process for each tab. So why not Mozilla and Google can do it in FF if Microsoft can do it in IE?
Because as the post you replied to said, it's a huge change. I don't know what MS did for IE, but changing an application to be built on processes instead of threads likely means rebuilding it from the ground up. I don't mean the rendering engine - that's probably mostly fine, but all the UI shell would need to be reworked to support communication between processes. It's a huge effort.
RE[4]: Reinventing the wheel :(
by sbergman27 on Tue 23rd Dec 2008 23:12
in reply to "RE[3]: Reinventing the wheel :("
...but all the UI shell would need to be reworked to support communication between processes. It's a huge effort.
Meaning exactly the sort of thing that Mozilla Corp would never have considered without being shown up by real FOSS competition on their own doorstep. Isn't it wonderful that they now have such competition? I'm a Linux user, so I can't use Chrome (natively) yet, and don't really care for the Codeweavers solution. But I'm delighted that Chrome exists. And I look forward to full integration of Webkit in Epiphany 2.26 or 2.28.
RE[4]: Reinventing the wheel :(
by microFawad on Wed 24th Dec 2008 17:35
in reply to "RE[3]: Reinventing the wheel :("
I don't know what MS did for IE, but changing an application to be built on processes instead of threads likely means rebuilding it from the ground up
"IE8 uses the Loosely Coupled Internet Explorer (LCIE) architecture and runs the browser frame and tabs in separate processes"
http://en.wikipedia.org/wiki/Internet_Explorer_8#Performance_and_st...





Member since:
2005-12-09
First of all every browser today is multithreaded but the new thing that Google had done is to create a new process for each tab instead of creating a new thread for each tab.
Do you know that IE8 is doing same thing that Chrome did. I mean creating a new process for each tab. So why not Mozilla and Google can do it in FF if Microsoft can do it in IE?