Linked by Thom Holwerda on Mon 8th Apr 2013 16:59 UTC
Internet & Networking Peter Bright has summarised some of the post-fork discussions on the WebKit mailinglists. "Now that Google is going its own way and developing its rendering engine independently of the WebKit project, both sides of the split are starting the work of removing all the things they don't actually need. This is already causing some tensions among WebKit users and Web developers, as it could lead to the removal of technology that they use or technology that is in the process of being standardized. This is leading some to question whether Apple is willing or able to fill in the gaps that Google has left." There's a clear winner and loser here.
Thread beginning with comment 558004
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Different question?
by jared_wilkes on Tue 9th Apr 2013 00:39 UTC in reply to "RE[3]: Different question?"
Member since:

I did not say Apple has to do nothing.

I said that if Webkit users stick with Apple's WebKit but continue to have dependencies on Google's contributions, that is that user's and Google's problem; if other WebKit users use Google's webkit, Apple doesn't have a problem (i.e. a relations problem) obligating them to support code Google contributed and then abandoned (if they refuse to support it, I actually imagine they will assist transitions).

The majority of argument in the article is about code that does not ship/is only available to "developers" who know they are "beta-testing".

Reply Parent Score: 2