Re:Why you should never use Socket.IO
by josephg on Wednesday November 09, 2016 @12:14AM
(#12906267)
I can second this. I spent 2 months fielding bug reports against ShareJS all caused by terrible design mistakes in socket.io. I ended up being forced to write my own long polling library[1] just because of how unstable socket.io was.
But today anyone building new applications should use websockets. Browser support is excellant, speed is great, firewall penetration is fantastic if you run your site on HTTPS. You gain cross-server language compatibilty, you avoid socket.io's awful design decisions around reconnection, error handling and code quality.
Re:Why you should never use Socket.IO
by zappo2938 on Wednesday November 09, 2016 @12:14AM
(#12906265)
It looks like µWebSockets has bindings to Node.js. This is good to know.
Socket.IO came out years ago. Yes, it is slow compared to recent implementations, but it's still valuable to give props to your predecessors.
Re:Why you should never use Socket.IO
by alexhultman on Wednesday November 09, 2016 @12:10AM
(#12906248)
WebSocket++ was written at the same time as Socket.IO and performs about 30x better. I give credit where credit is due. I also criticize projects where criticism is due.
I would recommend WebSocket++ or libwebsockets (if you are not going with µWebSockets).