Streaming requests with fetch - HTTP 203
Jake and Surma chat about a new experiment landing in Chrome 85 - streaming request uploads with the fetch API. Some links we mentioned: The 'year' of streams → https://goo.gle/3iAQoIB TextDecoder, as a fallback to TextDecoderStream → https://goo.gle/3gSAFo5 Compression streams → https://goo.gle/2DRqtOj Reactive programming with streams → https://goo.gle/3iCTFqU The router issue → https://goo.gle/30TeAjK The 'sockets' demo → https://goo.gle/3gUHci3 This episode as an article, including origin trial details → https://goo.gle/3kFNCUu Also, if you enjoyed this, you might like the HTTP 203 podcast! → https://goo.gle/2y0I5Uo Other videos in the series → https://goo.gle/2wneQLl Subscribe to Google Chrome Developers here → https://goo.gle/ChromeDevs Also, if you enjoyed this, you might like the HTTP203 podcast! → https://goo.gle/2y0I5Uo

Weak JavaScript - HTTP 203

Top 10 performance pitfalls - HTTP 203

The Zombie DOM - old DOM stuff that still haunts us today | HTTP 203

From nothin’ to gzip - HTTP 203

Inside Anthropic, the $965 Billion AI Juggernaut | The Circuit

WTF Do These Even Mean

When Stupid Cops Mess With FBI Agent

WebAssembly Threads - HTTP 203

I Investigated The World's Skinniest vs Fattest City

3.143 ways to synchronize data across documents - HTTP 203

Slashing layout cost with content-visibility - HTTP 203

Cross-origin fetches - HTTP 203

Node JS - HTTP Streaming

Jake Archibald on the web browser event loop, setTimeout, micro tasks, requestAnimationFrame, ...

Ethan Arrowood | Node.js Streams vs Web Streams - A performance and Implementation Deep Dive

The history API is dead. Long live the navigation API | HTTP 203

What the heck is the event loop anyway? | Philip Roberts | JSConf EU

Prime Reacts: The Flaws of Inheritance

Webhooks vs Websockets vs HTTP Streaming - Which Event-Driven API to use?

