Linked by Thom Holwerda on Mon 8th Apr 2013 16:59 UTC
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 557957
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:
2005-07-08
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.