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 557966
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Different question?
by jared_wilkes on Mon 8th Apr 2013 18:58 UTC in reply to "RE: Different question?"
jared_wilkes
Member since:
2011-04-25

Nonsense. The article takes the stance that if these organizations choose to stay with WebKit, that Apple may abandon them... which itself is nonsense. If these organizations go with Blink, then neither Apple nor these organizations have a webkit problem.

Reply Parent Score: 2

RE[3]: Different question?
by Thom_Holwerda on Mon 8th Apr 2013 19:08 in reply to "RE[2]: Different question?"
Thom_Holwerda Member since:
2005-06-29

If these organizations go with Blink, then neither Apple nor these organizations have a webkit problem.


Considering Apple's contributions to WebKit were tapering off substantially - contributors leaving WebKit will be a MAJOR problem for Apple if they don't step up their game.

I'm sure they will, but saying Apple doesn't have to do a thing is clearly false.

Reply Parent Score: 6

RE[4]: Different question?
by bowkota on Mon 8th Apr 2013 20:17 in reply to "RE[3]: Different question?"
bowkota Member since:
2011-10-12


Considering Apple's contributions to WebKit were tapering off substantially - contributors leaving WebKit will be a MAJOR problem for Apple if they don't step up their game.


Not really the case looking at the graph you yourself posted.
http://cdn.macrumors.com/article-new/2013/04/commits.png

Might want to have your eyes checked out.

Reply Parent Score: 3

RE[4]: Different question?
by jared_wilkes on Tue 9th Apr 2013 00:39 in reply to "RE[3]: Different question?"
jared_wilkes Member since:
2011-04-25

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