Media Summary: Jake and Surma talk about the importance of context when making performance optimizations and some common mistakes that ... In this episode, Jake makes the case that URLs are impossible for humans to interpret, especially when it comes to security. Surma reminds Jake of four weird browser bugs they ran into while building most of which Jake has blocked ...

Web Rtc Http203 - Detailed Analysis & Overview

Jake and Surma talk about the importance of context when making performance optimizations and some common mistakes that ... In this episode, Jake makes the case that URLs are impossible for humans to interpret, especially when it comes to security. Surma reminds Jake of four weird browser bugs they ran into while building most of which Jake has blocked ... In nodejs you can 'require' JSON. The same feature was added to the HTML spec, but then… it was removed. Jake and Surma ... Always the highlight of this event, Google provides the nitty gritty details on what they are doing to progress Jake chats to Surma about six ways you can synchronise data between documents, but some of them don't work all the time, so a ...

Jake and Surma talk about the JAMStack, what it means and how it's useful for web developers. 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

Web RTC - HTTP203
Context and Optimizations - HTTP 203
Humans can't read URLs. How can we fix it? - HTTP 203
Changing web standards - HTTP 203
Four silly browser hacks - HTTP 203
Importing JSON - ABANDONED - HTTP 203
VES203. WebRTC: The Future Champion of Low Latency
Google: What's next for WebRTC?
But… why HTTP 203?
3.143 ways to synchronize data across documents - HTTP 203
JAM Stack - HTTP 203
How we got into web development - HTTP 203
View Detailed Profile
Web RTC - HTTP203

Web RTC - HTTP203

Ever wondered about

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 ...

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.

Changing web standards - HTTP 203

Changing web standards - HTTP 203

Something a bit different for

Four silly browser hacks - HTTP 203

Four silly browser hacks - HTTP 203

Surma reminds Jake of four weird browser bugs they ran into while building https://proxx.app, most of which Jake has blocked ...

Importing JSON - ABANDONED - HTTP 203

Importing JSON - ABANDONED - HTTP 203

In nodejs you can 'require' JSON. The same feature was added to the HTML spec, but then… it was removed. Jake and Surma ...

VES203. WebRTC: The Future Champion of Low Latency

VES203. WebRTC: The Future Champion of Low Latency

Alex Gouaillard, CTO, millicast.

Google: What's next for WebRTC?

Google: What's next for WebRTC?

Always the highlight of this event, Google provides the nitty gritty details on what they are doing to progress

But… why HTTP 203?

But… why HTTP 203?

The show's called "

3.143 ways to synchronize data across documents - HTTP 203

3.143 ways to synchronize data across documents - HTTP 203

Jake chats to Surma about six ways you can synchronise data between documents, but some of them don't work all the time, so a ...

JAM Stack - HTTP 203

JAM Stack - HTTP 203

Jake and Surma talk about the JAMStack, what it means and how it's useful for web developers.

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 ...

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 ...