Web developers should care about web performance. Unfortunately web performance explanations usually start from the rendered website, go down to the DOM and stop with statements as ".. and it's fast because it's accelerated". We will do it the other way around: We will start with a pixel and work our way up: How does a piece of markup turn into pixels, how are they combined to the page? We will visit: Parsing Layers / Textures Painting Compositing / Transformations From this we will conclude what we need to do to help the platform make our sites slick and fast.Talk language: EN
Martin is open source contributor and web evangelist by heart from Zurich with a decade experience from the trenches of software engineering in multiple fields. He works as a software engineer at Archilogic in front- and backend. He devotes his time to moving the web forward, fixing problems, building applications and systems and breaking things for fun & profit. Martin believes in the web platform and is working with bleeding edge technologies that will allow the web to prosper.