Testing Chromium: ThreadSanitizer v2, a next-gen data race detector
lunes, 21 de abril de 2014
Chrome 35 Beta: More developer control over touch input, new JavaScript features, and unprefixed Shadow DOM
jueves, 10 de abril de 2014
Blink’s First Birthday
jueves, 3 de abril de 2014
We also built the Chromium Feature Dashboard, a tool for staying up-to-date on Blink’s web API surface. It’s currently tracking implementation of 168 web platform features and anonymous usage statistics for 295 JavaScript APIs & HTML tags and 428 CSS properties. We use these usage statistics to see which features can be safely deprecated. In the offline world, last September we held our first bi-annual contributors’ conference with over 160 participants from 10+ organizations.
On the technical side, code size and complexity remains an ongoing challenge for Blink. Code complexity slows development and leads to bugs. Fortunately, we’ve been able to aggressively remove and simplify our code because Blink’s only supported port is Chromium. In aggregate, nearly half the codebase has been eliminated since work on Blink began last year. Notable simplification efforts include unifying CSS and SVG animations with the Web Animations engine, replacement of our WebIDL compiler, factoring of a blink_platform layer out of core code, and continued work on a C++ garbage collector.
2014 promises an even greater increase in mobile computing, thus we continue to focus Blink’s efforts there. Software performance is critical on mobile devices because of constrained hardware and high user expectations. To improve mobile web performance, we have projects to speed up rendering, minimize binary size, reduce input latency, preserve battery power, shrink memory consumption, and more.
We’ve seen some results already. For example, the tight relationship between Blink and Chromium has allowed us to improve the abstraction layer between Blink and Chromium’s compositor. We’re now much more careful to do work for Blink only just before Chrome draws to the screen, avoiding wasting CPU cycles generating results that will overwritten before the next frame is drawn anyway. Through tighter integration, we’ve also achieved 50% savings in compositing updates that change only CSS transforms. This is just the beginning of our performance work; we expect even further improvements from newer efforts like GPU rasterization and better scheduling.
As we enter our second year, we plan to continue to improve Blink on mobile devices, grow our community, and fight the good fight against complexity creep. Join us or follow along to stay in touch!
Posted by Eric Seidel, Software Engineer and Code Complexity Curtailer
