Linked by Thom Holwerda on Wed 24th Feb 2010 16:52 UTC, submitted by Michael Oliveira
BeOS & Derivatives This is news that makes me very, very happy. Stephan "stippi" Assmus has written a lengthy blog post detailing the progress made on Haiku's WebKit port, and they're quite far along. Thanks to the help of several community members, the test browser, enticingly named (euh...) HaikuLauncher, is already relatively stable, supports tabbed browsing, and a whole lot more.
Thread beginning with comment 411053
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Chrome?
by anevilyak on Thu 25th Feb 2010 19:15 UTC in reply to "Chrome?"
Member since:

Is this browser based on Chrome? If not, why write a new browser from scratch? Does each tab run in a separate thread or a separate process?

Chrome, no, WebKit (the renderer used by Chrome, Safari, Arora and a few others), yes. Porting the entirety of Chromium would very much be a non-trivial undertaking, and for being included in the OS we want a smaller/more lightweight browser anyways. Someone could certainly port the full Chrome later if they so desired though, and the work we're already doing on WebKit would be required to do so anyways.

Currently each tab runs in the same process; running them in multiple threads has no real benefit, since a) WebKit currently requires all of its core actions to be executed from the same thread, and b) since threads share the same process/address space they offer no crash/security protection anyways, which is the primary goal of running them in separate processes. Multiprocess might come a little further down the road, but for the time being we have more than enough things to fix in our port of WebKit itself.

Edited 2010-02-25 19:17 UTC

Reply Parent Score: 2

RE[2]: Chrome?
by phoudoin on Fri 26th Feb 2010 16:34 in reply to "RE: Chrome?"
phoudoin Member since:

Regarding running each web page in his own thread, the design taken by Stephan does it half : while the layout is done by webcore in one single shared thread, the rendering is actually done by Haiku's app_server, which draw to every offscreen BView in a dedicated thread.

Multiple HaikuLauncher web view (tab or window, doesn't matter) means multiple threads. But on app_server side...

Reply Parent Score: 1