Media Summary: With so many brand new web features being gated on In this episode, Jake makes the case that URLs are impossible for humans to interpret, especially when it comes to security. From talking vDOM to lying to users, Paul & Jake are all about ensuring users get blazing fast sites. Watch more

Http 203 Https Everywhere S2 - Detailed Analysis & Overview

With so many brand new web features being gated on In this episode, Jake makes the case that URLs are impossible for humans to interpret, especially when it comes to security. From talking vDOM to lying to users, Paul & Jake are all about ensuring users get blazing fast sites. Watch more Jake and Surma talk about the importance of context when making performance optimizations and some common mistakes that ... Jake & Surma talk about web security, Spectre and Meltdown, and the ways that security teams are addressing vulnerabilities. In HTTP203 HTTP2, Paul and Jake talk on the future of

Jake has developed an allergic reaction to a vital substance, and Paul brings up the highly contentious topic of Web vs Native. In this episode, Surma explains a bit of the history of color spaces (sRGB, CIE XYZ, p3, rec2020, CIE LAB...) and why they are ... In a particularly self-indulgent episode, Jake and Surma chat about what got them into the web, and the things that helped along ... In this episode, Surma tells the story of how he found an interop bug in Chrome and patched it himself. You'd think the story ends ...

Photo Gallery

HTTP 203: HTTPS Everywhere (S2, Ep3)
Humans can't read URLs. How can we fix it? - HTTP 203
But… why HTTP 203?
HTTP 203: Performance Matters (S2, Ep5)
Context and Optimizations - HTTP 203
Web Security - HTTP203
HTTP2 - HTTP203
HTTP 203: Web Vs Native (S2, Ep1)
HTTP 203: Season 2 Teaser
Color Spaces: Do YOU know the difference between sRGB, LAB and CIE XYZ? - HTTP 203
How we got into web development - HTTP 203
Changing web standards - HTTP 203
View Detailed Profile
HTTP 203: HTTPS Everywhere (S2, Ep3)

HTTP 203: HTTPS Everywhere (S2, Ep3)

With so many brand new web features being gated on

Humans can't read URLs. How can we fix it? - HTTP 203

Humans can't read URLs. How can we fix it? - HTTP 203

In this episode, Jake makes the case that URLs are impossible for humans to interpret, especially when it comes to security.

But… why HTTP 203?

But… why HTTP 203?

The show's called "

HTTP 203: Performance Matters (S2, Ep5)

HTTP 203: Performance Matters (S2, Ep5)

From talking vDOM to lying to users, Paul & Jake are all about ensuring users get blazing fast sites. Watch more

Context and Optimizations - HTTP 203

Context and Optimizations - HTTP 203

Jake and Surma talk about the importance of context when making performance optimizations and some common mistakes that ...

Web Security - HTTP203

Web Security - HTTP203

Jake & Surma talk about web security, Spectre and Meltdown, and the ways that security teams are addressing vulnerabilities.

HTTP2 - HTTP203

HTTP2 - HTTP203

In HTTP203 HTTP2, Paul and Jake talk on the future of

HTTP 203: Web Vs Native (S2, Ep1)

HTTP 203: Web Vs Native (S2, Ep1)

Jake has developed an allergic reaction to a vital substance, and Paul brings up the highly contentious topic of Web vs Native.

HTTP 203: Season 2 Teaser

HTTP 203: Season 2 Teaser

HTTP 203 Season 2

Color Spaces: Do YOU know the difference between sRGB, LAB and CIE XYZ? - HTTP 203

Color Spaces: Do YOU know the difference between sRGB, LAB and CIE XYZ? - HTTP 203

In this episode, Surma explains a bit of the history of color spaces (sRGB, CIE XYZ, p3, rec2020, CIE LAB...) and why they are ...

How we got into web development - HTTP 203

How we got into web development - HTTP 203

In a particularly self-indulgent episode, Jake and Surma chat about what got them into the web, and the things that helped along ...

Changing web standards - HTTP 203

Changing web standards - HTTP 203

Something a bit different for

Surma’s Interop Adventure - HTTP 203

Surma’s Interop Adventure - HTTP 203

In this episode, Surma tells the story of how he found an interop bug in Chrome and patched it himself. You'd think the story ends ...