Linux - NewsThis forum is for original Linux News. If you'd like to write content for LQ, feel free to contact us.
All threads in the forum need to be approved before they will appear.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
A high-profile fork: one year of Blink and Webkit
In 2013 the browser wars sprouted a new rendering engine: Blink. When Blink forked in April 2013, Webkit had a total of 1.8 million lines of C++, 2,500 commits per month and was the most popular browser engine. On mobile, Webkit backed the top 3 browsers (Apple Safari, Google Chrome, Android Browser), accounting for the majority of mobile eyeballs. This post is a look at the Blink/Webkit fork one year later: how have the projects diverged, who is driving them, and what are they up to?
What is a browser engine?
By not understanding the subtle differences between the projects, the tech media reported Blink removed 8.8 million lines of code. How Blink manages to run on -7 million lines of code is a mystery. ("git diff --stat" shows that 8.8 million lines were removed post-fork in Blink, primarily layout test and supporting images.) A joke by Andreas Kling was later misreported as WebKit removing 8.8 million lines of ShadowDOM.
The projects are quickly diverging due to differences in resources and priorities. The graph below shows the differences in commit rate over time. Blink's faster trajectory isn't unexpected since Google was the top contributor to Webkit.