Note that Chromium has been doing this for a while with impl-side painting.<p>What is exciting about this in the context of Servo, though, is that it completes the parallel pipeline:<p>* Script can be parallelized through PJS or Web Workers.<p>* All phases of layout are fully parallelized: selector matching is performed in parallel (one micro-task per DOM node), layout is performed in parallel, and display list construction is performed in parallel (one micro-task per render object).<p>* Painting is now performed in parallel on a tile-by-tile basis.<p>* Compositing is performed in parallel thanks to the GPU.<p>All of these tasks can also be performed in parallel with one another.
This is also useful as a demonstration of how the Servo developers use bots to augment the review of pull requests. See also "bors", the Rust compiler's continuous integration bot: <a href="http://buildbot.rust-lang.org/bors/bors.html" rel="nofollow">http://buildbot.rust-lang.org/bors/bors.html</a><p>It would be very interesting to survey the largest projects being developed on Github to determine if they've also grown bespoke ways of dealing with the platform's pain points. I know that the Rust developers aren't entirely satisfied with the tools that Github provides (which seem to be optimized for small projects at the expense of large ones), but Github's network effects are just too good to ignore for a project that relies on volunteer contributions.