WebSocket
In this channel's material, WebSocket appears as Guillermo Rauch's canonical example of riding an early, messy wave: when he began building Socket.IO, WebSocket was barely a draft specification, and the gap he filled was between “I want real-time communication” and “I want to ship an application.” Socket.IO — the clean, opinionated solution he shipped on top of the immature spec — now powers sites like Perplexity.[^1b713f71-2dd6-5984-a0ec-0b6164c4c926@217]nnThe broader lesson the material draws from WebSocket: identify a technology “when it's just a few drops of water” — promising but extremely messy — and ship before it matures.[^1b713f71-2dd6-5984-a0ec-0b6164c4c926@217] Staying “terminally online” at the frontier of what's about to become possible is exactly how Rauch spotted WebSockets before browsers shipped them, the same instinct he later applied to v0 and AI.[^1b713f71-2dd6-5984-a0ec-0b6164c4c926@217]nn[^1b713f71-2dd6-5984-a0ec-0b6164c4c926@217]: Guillermo Rauch on spotting early waves — “you kind of want to identify the wave when it's just a little a few drops of water but you have that you see that potential and it's also extremely messy” (Vercel's Guillermo Rauch on AI and the Future of Coding - Ep. 47).