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 557959
To read all comments associated with this story, please click here.
by butters on Mon 8th Apr 2013 17:50 UTC
Member since:

What would Samsung do?

Stick with the Apple-driven WebKit stack?
Adopt the Google-driven Chromium stack?
Flee to the Mozilla-driven Gecko stack?

Although it may not be the primary consideration here, Google is forcing Samsung to make a decision about TouchWiz. Their choice will shed some light on their forward plans -- as an Android vendor or a defector.

Reply Score: 3