So it would have less C++ code but more JS.
That was always the case, even when they both used WebKit. Apple didn't include many of the "next-gen webapps" stuff that Google implemented, like IndexedDB. They were always more focused on CSS, for example.
Hopefully there's a silver lining to the Blink fork: more differentiated renderers in the wild means that web developers will have to rely more on standards again, instead of going nuts with "-webkit" prefixes and Chrome-only apps.
But actions speak louder than words. Some awesome webapp-focused stuff that's been just recently announced: IndexedDB, WebGL, JavaScript Promises, Media Source Extensions, Web Crypto, a vastly improved JavaScript VM that scales from super quick startup for simple pages to advanced optimizations for complex webapps, and massive optimizations for webapp responsiveness (covering DOM, rendering, layout, style, JS, etc). And that's just the announcements, there is a lot more cool stuff in WebKit nightlies like HTML templates, new ES6 language features, major web developer tools improvements, and more.
I have 2 suggestions for the presentation:
1. "Cumulative commits" 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 since 2013, i.e., 2013 is the baseline. Might be worth mentioning that explicitly.
2. "The players" graph has a nonlinear, seemingly arbitrary scale. This is potentially misleading as it looks like e.g. Samsung has 1/3 the commits of Google, when actually it is more like 1/10. Might be worth mentioning the scale is not linear, or just using a linear scale?
The players graph is tough. There are many 0 entries which means a true log scale is out. A linear graph ends up being dominated by Apple and Google so you can't really see the other organizations. I should call out the scale more explicitly though. Btw, the scale is technically a sqrt scale: https://github.com/mbostock/d3/wiki/Quantitative-Scales#sqrt
It's a hard problem, but I really think non-linear scales obfuscate more than they clarify for stuff like this. Non-linear scales should be used to eliminate variables not relevant to the analysis. That Google is 10* Samsung is part of, and not extrenuous to, the analysis here.
http://techcrunch.com/2013/05/16/google-has-already-removed-...
As I understand it, Google and Apple did things like sandboxing in different ways for Chrome and Safari, and so there was a lot of code in both projects that could be ripped out once the alternate way of doing things didn't need to be supported any more.
But, just to let you know, Konqueror has the ability to use multiple engines. It supports both KHTML and Webkit.
You could have a tab rendered with KHTML and another one with Webkit.
I thought Blink probably wanted to change some things about the compositor (ScrollingTree/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'm curious if there's anything neat I'm missing out on :).
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!).
