3 ms·
Why is this important: https://developers.google.com/web/fundamentals/performance/rendering/ https://developers.google.com/web/fundamentals/performance/r... TL
by warpech 9y ago
Why is this important: https://developers.google.com/web/fundamentals/performance/rendering/ https://developers.google.com/web/fundamentals/performance/r...
TL;DR rendering performance
- littlestymaar 9y agoYou should take these advices with a grain of salt because it refers to the legacy rendering pipeline used by current web browers. There is not absolute rule stating that layout and painting must be slow while compositing is not. In fact Mozillians are currently working on a new rendering pipeline[1] based on state of the art rendering tools[2]. This new pipeline should be deployed in firefox in 2018 as a part of the ongoing Quantum project. [1] https://github.com/servo/webrender https://github.com/servo/webrender [2] https://m.youtube.com/watch?v=BTURkjYJ_uk https://m.youtube.com/watch?v=BTURkjYJ_uk
- ryanpetrich 9y agoSeems hardly legacy if it's the rendering pipeline used in all browsers' current release versions. (and I say this as a WebRender enthusiast)
- striking 9y agoYeah, but it makes sense to follow it now, as it affects us now and will continue to do so through at least 2018, until everyone has updated their renderer.