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 557694
To view parent comment, click here.
To read all comments associated with this story, please click here.
henderson101
Member since:
2006-05-30

Well, no... quite clearly, one or two Google/Chromium devs are arguing with an Apple/Webkit2 dev over the multiprocess extensions. The Apple guy was actually part of the process and has first hand knowledge of the rational behind Webkit2, the Chromium guys are less well informed on the situation. I'm pretty much going to believe the guy who was actually part of the decision as to why it was made, and both the Chrome/Googlers conceded anyway.

Reply Parent Score: 2

Tony Swash Member since:
2009-08-22

I'm pretty much going to believe the guy who was actually part of the decision as to why it was made, and both the Chrome/Googlers conceded anyway.


Me too

Reply Parent Score: 1

PresentIt Member since:
2010-02-10

I'm not sure... Apple's behavior in the Webkit project has been pretty damn shady at times.

Reply Parent Score: 2

henderson101 Member since:
2006-05-30

Not in this case. The guy in question has publicly identified himself as being an Apple Webkit2 developer *and* gone on record that they *did* speak to Google regarding the specific Chrome functionality being folded back in to Webkit and Google declined their request.

To be honest, this is an old criticism, and most of the so called "shady" Webkit development was early on when the project was publicly announced.

Reply Parent Score: 2