How to Build a Real-Time Chat App with WebSockets (And Why It Works)

So I saw a thread recently where a developer got marked down in a course for suggesting WebSockets and TCP as the foundation for a chat application. The instructor insisted that PHP was the only valid approach for web development. Look, I'm not here to bash PHP — I've shipped production PHP code and it pays bills. But if someone tells you WebSockets aren't a legitimate approach for real-time chat, that's a fundamental misunderstanding of how the modern web works. Let me walk you through exactly why WebSockets exist, how they solve the real-time problem, and how to build a working chat app with them. The Core Problem: HTTP Wasn't Built for Real-Time HTTP follows a request-response model. The client asks, the server answers. That's it. If you want to build a chat app on pure HTTP, you're stuck with one of these workarounds: Polling: Hit the server every few seconds asking "any new messages?" Wasteful, laggy, and brutal on your server at scale. Long polling: Hold the connection open until