WebKit2 is Coming, More Stable than Ever Before
Recently, one of the Apple employers has announced a new WebKit framework, that they call WebKit2.
One of the main framework goals is to utilize a split process model, so the web content would be placed into a separate process. As a result, bad plugin, tab etc. won’t crash the whole web browser.
This behavior is very similar to Chrome’s; however, as split process module is directly integrated into WebKit2 framework, other clients will be able to use it as well.
As for today, initial versions are available for Windows and Mac platforms.
[digg-reddit-me]
Thanks to Blake for the news tip.
About (Author Profile)
Vygantas is a former web designer whose projects are used by companies such as AMD, NVIDIA and departed Westood Studios. Being passionate about software, Vygantas began his journalism career back in 2007 when he founded FavBrowser.com. Having said that, he is also an adrenaline junkie who enjoys good books, fitness activities and Forex trading.
Subscribe
If you enjoyed this article, subscribe to receive more just like it.
Which means all webkit browsers will effectively become huge RAM hogs, just like Chrome.
This is awesome news for Gecko! Yet another set to keeping Firefox on top of the RAM economy list, even more now that plugin sandboxing (or whatever it is) is implemented!
Opera’s got the right idea about RAM I’d say.
When there’s much RAM to spare Opera uses it, but as the RAM get scarce, it releases the harsh grip on any amount it doesn’t need.
Yeah, that’s why Opera is the lightest browser on RAM limited computers. It’s very good.
Apart from Firefox’s numerous memory leaks, Gecko is also getting this. You’ll have Firefox’s memory leaks in addition to eating more memory per tab!
Funny. I never noticed any memory leaks, and Firefox is the lightest browser of all five major browsers…
Firefox is not getting this: Firefox is getting out of process plugins. It’s not this.
Unless this is basically out of process plugins.
In any case, Firefox is getting them in 3.6.4 already.
Firefox is getting this: https://wiki.mozilla.org/Electrolysis
As always, Chrome innovates while Firefox follows :D
Chrome is hardly innovative in anything TBH.
Electrolysis is only out of process plugins, not tabs.
Dude, read the wiki page.
Actually, Chrome didn’t innovate anything. Google copied this feature from IE.
Bye bye, Firefox :D
As I said above, Firefox is going to get out of process plugins very soon. In fact, there’s already a beta out there:
http://www.mozilla.com/firefox/lorentz/
The feature is isolated in that version, but it will be implemented in Firefox 3.6.4.
if anything, then it is opera that will suffer.
webkit replaced opera in almost all embeded envionments, even in adobe creative suite webkit rules now, opera is in wii (wonder how much longer), few handsets and (as opera mini) is preloaded to some phones.
webkit rooted out opera of oem market, and did that for a reason
WebKit can’t replace Opera in almost all embedded environments since Opera wasn’t even close to being in almost all embedded environments in the first place.
Wonder how you conclude that WebKit has pushed it out when Opera has announced lots of OEM deals lately.
Oh wait, it’s nobbie. Facts don’t matter to Firefox fanboys :D
why it’s trend to multi-process now? it is due to multi-core processor that get trend on 2000s? or because we got a huge GB’s RAM for cheap buck’s today?
why no one keep it safe with multi-thread… use garbage collector and release ram efficiently? using threaded jobs works faster than multi-process jobs isn’t?