Why WebRTC is the way it is.
summary
A first‑hand retrospective explaining why WebRTC evolved the way it did, naming specific technologies and design areas such as RTP, SDP signalling, the DataChannel protocol choice, codecs, encryption decisions, and the P2P versus client–server tradeoff. The speaker draws on early involvement in standardisation and API implementation to trace starting points, key forks in decisions, and mistakes that shaped WebRTC’s APIs and architecture.
AI-written summary · about







