Good question. I see this more or less like chicken-egg situation. Right now it seems that client side is quite well maturing. Client side is the easier part of

Good question. I see this more or less like chicken-egg situation. Right now it seems that client side is quite well maturing. Client side is the easier part of websockets. PHP's whole model is 'shared nothing', that's why it fits so poorly with websockets. 'Real-time' two-way communication with the server and the clients is getting more and more common in web apps, and even web sites. I'm not sure how the server side of the websockets are going to be solved. If PHP gets it right, it will probably have great future ahead. These days we need to revert to dual solution, main system behind Apache or Nginx, and websockets with for example custom node.js servers. It is far from optimal.