4 ms·
Do we know why Google grew dissatisfied with Apple and forked Webkit?
by remir 8y ago
Do we know why Google grew dissatisfied with Apple and forked Webkit?
- mda 8y agoGenerally, it was slowing each team down to implement new features.
- saagarjha 8y agoI believe Google felt that WebKit was too bloated for their taste. When they forked they ripped out quite a bit of code they did not need.
- ams6110 8y agoDo we know why Google grew dissatisfied with sites serving their own content and developed AMP?
- fastball 8y agoBecause sites serving their own content were generally slower, and slower load times means fewer ad clicks. Google making the web faster is a mutually beneficial arrangement.
- no_wizard 8y agoFrom what I understand, it had to do with how fast Apple was upstreaming their changes/patches, a big part of which would require Apple to accept the modifications to Webkit core. https://arstechnica.com/information-technology/2013/04/google-going-its-own-way-forking-webkit-rendering-engine/ https://arstechnica.com/information-technology/2013/04/googl...
- sangnoir 8y agoYes - it project complexity was becoming unmanageable due to difference in multiprocessing architectures[1] of WebKit and Chromium. 1. https://blog.chromium.org/2013/04/blink-rendering-engine-for-chromium.html https://blog.chromium.org/2013/04/blink-rendering-engine-for...
- Phrodo_00 8y agoDo we know why apple didn't just push patches to khtml? Companies will just want control over their development pipeline