The future of chat

on YouTube ↗01h 18m

" summary

Argues real‑time apps require two things: minimal latency and self‑updating state, quantifies initial TCP importance around 100 milliseconds and the first 14 kilobytes, recommends server‑side render of visible data, uses optimistic updates plus client‑generated UIDs with idempotent server ops to avoid duplicates, embraces ES6/Babel modules and pure declarative UI, shows a working WordPress video player and a Sokkado evolution dashboard and tools (insights, P2P) that validate these patterns in practice.

AI-written summary · about

" chapters (11)

1. 0:00Start
2. 0:49Hello World Application
3. 3:49Key Aspects That Make a Real-Time Application
4. 5:52What Makes an Application Fast
5. 8:58Masking Latency
6. 17:13Eggman Script 6
7. 21:39The Programming Model
8. 23:46Subscription to the Server
9. 37:21Fuzz Testing
10. 55:46Coding Style
11. 59:10Code Base to Es6

" related talks

• 24mBuilding Realtime Singlepage AppsHenrik Joreteg · NodeConf 2011
• 54mHow to build the modern, optimistic and reactive user interface, we all want.Guillermo Rauch · ColdFront 2014
• 18mThe need for speed - Single-page apps, Optimistic UIs, ReactivityGuillermo Rauch · dotJS 2013
• 49mThe Real Time Web with XMPPJack Moffitt · JSConf 2009
• 32mVue Real-Time AppsNico Devs · MadVue 2026
• 22mEvery Node.js app should have real-time collab featuresVladi Stevanovic · Conf42 JavaScript 2023
• 21mWhy Real Time MattersSimen Skogsrud · Next.js Conf 2020
• 09m0-60 in 15 Minutes: Building a Realtime App With Elm and HorizonAbadi Kurniawaan · Elm Conf 2016