TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

The real reason why Google forked WebKit

3 点作者 esalazar大约 12 年前

1 comment

claudius大约 12 年前
&#62; There's no doubt that Apple has effectively managed the project and transformed it into a capable post-PC era rendering engine, but it is clear that if Google can eliminate 4.5 million lines of code from the project, then there's a lot of dead wood in there<p>That’s not really dead wood but merely wood unusable to Google, i.e. the threaded rendering engine WebKit2, which Google doesn’t want to use.<p>Certainly it is perfectly fine for Google to prefer having their own codebase, but claiming that WebKit carries 4.5M unused SLOC around is a little strange[0].<p>[0] Though I am sure that there <i>are</i> N unused SLOC in any project with M SLOC for some N≤M.