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.
Permalink for comment 557964
To read all comments associated with this story, please click here.
RE: Comment by Luminair
by Radio on Mon 8th Apr 2013 18:52 UTC in reply to "Comment by Luminair"
Member since:

Quite the opposite - if Apple does its work properly. The WebKit code will be cleaner and better tied up, with Apple's own JavaScript engine and multiprocess architecture. Blink's code too, with Google's own engine and architecture.

As long as standards are respected, and quirks and bugs are smashed, nobody loses.

Reply Parent Score: 8