HTTP/3 solves TCP head-of-line blocking by moving multiplexing from the application layer into the transport layer using QUIC over UDP. While HTTP/2 multiplexes streams over a single TCP connection (causing all streams to block when one packet is lost), HTTP/3 gives each stream independent ordering and recovery. The newsletter also covers Cursor's agentic coding system using MoE, speculative decoding, and context compaction for 4× speed improvements; Git's internal architecture with blobs, trees, commits, and tags stored in the .git directory; NAT's port mapping mechanism for sharing public IPs; and building computer vision apps with Ring APIs.
Table of contents
You.com Founders Predict an AI Winter Is Coming in 2026HTTP/2 over TCP vs HTTP/3 over QUICHow Cursor Agent WorksHow Git Really Stores Your DataHow NAT WorksBuilding a Computer Vision App on Ring APIsWe’re HiringSort: