 Hey everybody, what's up? It's Rob. We are back at the Progressive Web App Summit. I am joined by the one and only CIRMA. CIRMA, you just gave a talk on HTTP 2. It's a great word. I always mess it up. So I'm wondering for you, I'm not like a super networking pro. Can you tell me what is sort of the difference between HTTP and HTTP 2? So first of all, you can call it H2 because that is the official symbol, which makes it much much easier to say. There's two sizes. So most importantly, there is no big difference in terms of how the semantics of the protocol work. So all the web apps remain working the same. It's the request response. You still have the verbs, you have headers and the payload. So all that stays the same. The only thing that is actually different is how it goes over the wire. So instead of having at most six connections and each connection can only handle one, which was the case in H1. You can now only have one connection, but each of these individual streams, as they are called, can utilize this one connection to the fullest. So you don't have this head of line blocking issue anymore where you have to wait for a response to come in before you can send out the next request. So that means that things like bundling your JavaScript together or spreading your images are essentially counterproductive in HTTP 2. So stop doing that. Okay. And particularly for progressive web apps, did we get something, is there a cool benefit of using H2 for PWA? Well, apart from what I just said, there's also the, when you don't do bundling anymore, you get better caching because you can cache all the files individually because you don't do co-cache generation anymore, which means that apps tend to load faster. And then there's a new feature in HP2 called push, which allows you to push resources to watch the client that the client hasn't even requested yet. So when someone wants to have your index HTML, you pretty much know that they are going to request your JavaScript in your CSS as well. So you can just put that into their cache without them asking for it. And by the time the browser knows it needs it, it's already there. So that will basically make your app even more snappier and get it on screen so much faster. Okay. Now, I'm sold. That sounds awesome. I'm wondering, are there any tools or like, what is a good way for me to get started with H2? It's there. Well, I wrote a tool called Simple HTTP Server, which, if you know Python, there is the Simple HTTP Server, which basically serves the current directory. And I rewrote it in Go. So, and I'll just go because I wanted to have it on Windows, MacOS, and Linux alike, and it uses HTTP 2, obviously. For HTTP 2, you do need TLS, which can be very tedious, and that is why I wrote this tool because it generates that certificate for you. So you don't have to do it. It also has support for push, so you can actually just start it up and see what the impact on your app is when you switch to HTTP 2, which I think is really helpful. Cool. All right. So we will include a link to the fancy server, the Simple Go server for H2 down in the description. Also, links to Serma's talks and all of the other talks from the Progressive Web App Summit are available on the playlist. Serma, thank you so much for being with us today. I'm Rob Dodson from Beautiful Amsterdam here at the PWA Summit, signing off.