A high-profile fork: one year of Blink and Webkit

&gt; My high-level take on the past year is that the Blink project has been more focused on next-gen webapps with a heavy focus on the compositor, scheduling, and style subsystems. The WebKit project has been more focused on documents and improving existing pages with faster line layout and style selection (as well as an enormous amount of great work on JSC and bindings).<p>That was always the case, even when they both used WebKit. Apple didn&#x27;t include many of the &quot;next-gen webapps&quot; stuff that Google implemented, like IndexedDB. They were always more focused on CSS, for example.

Very interesting stuff! Kudos for taking the time to put this together.<p>I have 2 suggestions for the presentation:<p>1. &quot;Cumulative commits&quot; looks like it starts from 0 in 2013, and that total commits doubled in the two projects over a few months. This is potentially misleading - I assume this is showing additional commits <i>since</i> 2013, i.e., 2013 is the baseline. Might be worth mentioning that explicitly.<p>2. &quot;The players&quot; graph has a nonlinear, seemingly arbitrary scale. This is potentially misleading as it looks like e.g. Samsung has 1&#x2F;3 the commits of Google, when actually it is more like 1&#x2F;10. Might be worth mentioning the scale is not linear, or just using a linear scale?

i find the treemap graphs under &quot;Priorities and revealed preferences&quot; very difficult to parse. there are a lot of the same files in there with different colors. pretty poor viz choice IMO.

&gt; the Blink project has been more focused on next-gen webapps with a heavy focus on the compositor, scheduling, and style subsystems.<p>I thought Blink probably wanted to change some things about the compositor (ScrollingTree&#x2F;ScrollingConstraints being separate, for example) more than doing new work on it. The WebCore compositor is in pretty good shape (composited position sticky, etc) so I&#x27;m curious if there&#x27;s anything neat I&#x27;m missing out on :).<p>I know that the Chromium Compositor (outside of Blink) has had significant upgrades in the last year, though (Chrome for Android can now scroll without dropping frames on every tile boundary -- huzzah!).

ShadowDOM is a key new web technology - hope Apple will get it one day - even MS is considering adding ShadowDOM to IE <a href="http://status.modern.ie/shadowdomunprefixed" rel="nofollow">http:&#x2F;&#x2F;status.modern.ie&#x2F;shadowdomunprefixed</a>

I thought Blink was trying to Implement the DOM in JS?<p>So it would have less C++ code but more JS.

What a great bit of dataviz. Would love to see similar for OpenSSL vs LibreSSL.

I&#x27;m curious what the 300,000 lines of code removed in Blink were, and the corresponding but smaller removal of code in WebKit.

They&#x27;re both KHTML to me.<p><a href="https://en.wikipedia.org/wiki/KHTML" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;KHTML</a>