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 557955
To read all comments associated with this story, please click here.
Different question?
by jared_wilkes on Mon 8th Apr 2013 17:29 UTC
Member since:

Why should Apple support technology abandoned by Google in WebKit?

If you are a developer who is dependent on V8 or other Google code, why would you moan at Apple rather than moaning at Google?

Reply Score: 2

RE: Different question?
by butters on Mon 8th Apr 2013 17:38 in reply to "Different question?"
butters Member since:

The JS engines are essentially interchangeable from the perspective of web developers. CSS is the primary venue for fragmentation, and HTML to a lesser extent.

The problem here is that Google was contributing support for variable assignment in CSS, which is a W3C draft standard proposed by Mozilla and also supported by Google. Now that Google has left WebKit, Apple does not intend for WebKit to support this standard.

Reply Parent Score: 7

RE: Different question?
by Radio on Mon 8th Apr 2013 18:46 in reply to "Different question?"
Radio Member since:

All wrong. In the example presented in the article, the technology isn't abandonned by Google, they keep it in Blink and it is on the way to becoming a standard.

It is Apple engineers who are close to causing fragmentation by mindlessly abandoning this future standard css property.

Edited 2013-04-08 18:46 UTC

Reply Parent Score: 3

RE[2]: Different question?
by jared_wilkes on Mon 8th Apr 2013 18:58 in reply to "RE: Different question?"
jared_wilkes Member since:

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[2]: Different question?
by jared_wilkes on Tue 9th Apr 2013 00:43 in reply to "RE: Different question?"
jared_wilkes Member since:

The example you are referencing is only in Chromium. It's recent, beta code of a beta feature. Apple is not responsible for supporting this code. Intimating that it is is nonsense. Safari (on desktop and mobile) has always been competitive and a good exemplar of a browser provider in supporting and improving CSS (both when it led and when it followed in supporting new standards).

Reply Parent Score: 2