Linked by Thom Holwerda on Wed 3rd Apr 2013 22:27 UTC
Google It's apparently browser engine day today. After Mozilla and Samsung announcing Servo, Google has just announced it's forking WebKit into Blink. Like WebKit, Blink will be open source, and it will also be used by other browser makers - most prominently, Opera has already announced it's not using WebKit, but Blink. Update: Courtesy of MacRumors, this graph illustrates how just how much Google contributed to WebKit. Much more than I thought. Also, Chrome developer Alex Russell: "To make a better platform faster, you must be able to iterate faster. Steps away from that are steps away from a better platform. Today's WebKit defeats that imperative in ways large and small. It's not anybody's fault, but it does need to change. And changing it will allow us to iterate faster, working through the annealing process that takes a good idea from drawing board to API to refined feature."
Thread beginning with comment 557571
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Comment by Nelson
by Radio on Thu 4th Apr 2013 09:22 UTC in reply to "Comment by Nelson"
Member since:

I'm interested into what broke down between Apple, Google, and the planning for WebKit2 (which was supposed to bring multi-process support) to lead to this. Its a rather drastic move.

"On higher levels than just WebCore, Apple has actually been using WebKit2, which handles things like sandboxing (the feature that allows one tab to crash without bringing the whole browser down). Die hard Chrome fans may be aware, but Google already has its own method for sandboxing tabs and has no need for WebKit2's implementation. However, WebCore contains a lot of code that is designed to support features like that. How much is "a lot of code," you ask? About 4.5 million lines of code, it seems. "

Reply Parent Score: 3

RE[2]: Comment by Nelson
by Nelson on Thu 4th Apr 2013 16:49 in reply to "RE: Comment by Nelson"
Nelson Member since:

I think this is a given, they disagreed on a large component so Google will excise that component from their fork.

I'm more interested in why, and I don't think this would've been a chief motivator for a fork. I think its a good bullet point on a list of reasons why, but the overarching goal here seems to be to have the freedom to set the agenda for their rendering engine.

Reply Parent Score: 2

RE[3]: Comment by Nelson
by _txf_ on Thu 4th Apr 2013 17:19 in reply to "RE[2]: Comment by Nelson"
_txf_ Member since:

freedom to set the agenda for their rendering engine.

well, they state that they couldn't do certain security fixes in webkit (but only relevant to chrome) because it would break things for others. So freedom to do anything they want without worrying about others certainly seems like the main reason.

Reply Parent Score: 2