News for hackers. Stuff that matters.
Re:Google Forks WebKit And Launches Blink, A New Rendering E... by ChuckMcM on Wednesday April 03, 2013 @05:22PM (#5489203)
" the decision to fork WebKit was entirely driven by the engineering teams and solely based on the fact that the engineers felt constrained by the technical complexity of working within the WebKit ecosystem."

Is this code for "They wouldn't take our changes so we said, 'Fork it!' and made our own." ?

Re:Google Forks WebKit And Launches Blink, A New Rendering E... by dragonwriter on Wednesday April 03, 2013 @05:44PM (#5489369)
> Is this code for "They wouldn't take our changes so we said, 'Fork it!' and made our own." ?

I think its probably more exactly what it says -- a way of eliminating the overhead of dealing with the complexity of the WebKit ecosystem. As noted in the article, "Google says, for example, that it will be able to remove 7 build systems and delete more than 7,000 files comprising more than 4.5 million lines right off the bat."

That's a whole lot of complexity that isn't relevant to what Google is doing with Chrome that is worth not having to deal with.

Re:Google Forks WebKit And Launches Blink, A New Rendering E... by stock_toaster on Wednesday April 03, 2013 @06:16PM (#5489605)
This[1] other article infers that those lines/files are related to webkit2 features of multiprocessing and sandbox code.

So it seems to me that ChuckMcM may not be far off.

[1]: http://arstechnica.com/information-technology/2013/04/google...

Re:Google Forks WebKit And Launches Blink, A New Rendering E... by justinschuh on Wednesday April 03, 2013 @11:37PM (#5490825)
Nope. If Google wanted to push things through it would certainly be possible as the single largest contributor, but that's not a productive way for anyone to participate. Instead, it's just a matter of simple project divergence. Apple landed the WebKit2 layer a few years ago, which was largely incompatible with the Chrome architecture that predated it by several years. Some minor efforts were made to unify parts, but WebKit2 continued to move in a direction that was increasingly incompatible with the existing Chrome architecture. Rather than burden everyone by continuing to maintain a codebase between these increasingly divergent approaches, it made sense to split.
Re:Google Forks WebKit And Launches Blink, A New Rendering E... by drivebyacct2 on Wednesday April 03, 2013 @06:07PM (#5489533)
Pretty sure it has more to do with their architecture changes RE: multithreading and embedding/porting.
Re:Google Forks WebKit And Launches Blink, A New Rendering E... by mooism2 on Wednesday April 03, 2013 @05:40PM (#5489344)
“Currently, the majority of WebKit reviewers are from Google (95), with Apple coming in second (59)... Google is also currently responsible for the vast majority of commits to the WebKit repository...”

Doubtful.

Re:Google Forks WebKit And Launches Blink, A New Rendering E... by coldtea on Wednesday April 03, 2013 @06:15PM (#5489596)
Numbers are doubtful?

I mean, sure, one could fabricate them, but why, especially if he can easily be caught doing it? Those are things anybody can verify by looking at the repository stats.

Here's what I found with a cursory look: Google has overtook Apple in commits 2-3 years already:

http://blog.bitergia.com/2013/02/06/report-on-the-activity-o...

Older stats (already Google on top): http://neugierig.org/software/chromium/notes/2010/02/webkit-...

And a TechCrunch article on the issue: http://techcrunch.com/2010/02/06/google-apple-webkit/

Re:Google Forks WebKit And Launches Blink, A New Rendering E... by mooism2 on Thursday April 04, 2013 @04:07AM (#5491539)
Sorry, I meant that the suggestion in the comment I was replying to (that Google was forking because they couldn't get their changes in) was doubtful, not that the figures I quoted from the article were doubtful (I was using them as justification for my comment).
Re:Google Forks WebKit And Launches Blink, A New Rendering E... by ChuckMcM on Wednesday April 03, 2013 @06:33PM (#5489706)
Reading through some of the analysis I agree, the story about the amount of glue necessary getting worse rather than better was pretty compelling. As a systems guy I find it amazing how intertwined the various parts are, between the process model to the rendering model, simplification there can only be good.
Re:Google Forks WebKit And Launches Blink, A New Rendering E... by mirsadm on Wednesday April 03, 2013 @06:08PM (#5489538)
Do you have any proof that the statement is false?
Re:Google Forks WebKit And Launches Blink, A New Rendering E... by mooism2 on Thursday April 04, 2013 @04:12AM (#5491551)
No, I was using the statement to cast doubt on the parent comment's suggestion.

And then I got a good night's sleep, waking up to find that I'd communicated the opposite of what I meant and that it's too late to edit my comment.

Re:Google Forks WebKit And Launches Blink, A New Rendering E... by hp50g on Wednesday April 03, 2013 @06:24PM (#5489664)
Reviewers and number of commits aren't really relevant stats. I'm the top committer and code reviewer at my company but it doesn't mean I write the most code :)