I couldn't even recall how many times I've done this already, but in 2017 I am once again showing up in the cold and grey city called Brussels and the lovely FOSDEM conference, to talk. (Yes, it is cold and grey every February, trust me.) So I had to go back and count, and it turns out 2017 will become my 8th straight visit to FOSDEM and I believe it is the 5th year I'll present there.First, a reminder about what I talked about at FOSDEM 2016: An HTTP/2 update. There's also a (rather low quality) video recording of the talk to see there.
I'm scheduled for two presentations in 2017, and this year I'm breaking new ground for myself as I'm doing one of them on the "main track" which is the (according to me) most prestigious track held in one of the biggest rooms - seating more than 1,400 persons.
You know what's cool? Running on billions of devices
Thousands of contributors help building the curl software which runs on several billions of devices and are affecting every human in the connected world daily. How this came to happen, who contributes and how Daniel at the wheel keeps it all together. How a hacking ring is actually behind it all and who funds this entire operation.
So that was HTTP/2, what's next?
A shorter recap on what HTTP/2 brought that HTTP/1 couldn't offer before we dig in and look at some numbers that show how HTTP/2 has improved (browser) networking and the web experience for people.
Still, there are scenarios where HTTP/1's multiple connections win over HTTP/2 in performance tests. Why is that and what is being done about it? Wasn't HTTP/2 supposed to be the silver bullet?
A closer look at QUIC, its promises to fix the areas where HTTP/2 didn't deliver and a check on where it is today. Is QUIC perhaps actually HTTP/3 in everything but the name?
Depending on what exactly happens in this area over time until FOSDEM, I will spice it up with more details on how we work on these protocol things in Mozilla/Firefox.
This will become my 3rd year in a row that I talk in the Mozilla devroom to present the state of the HTTP protocol and web transport.