Re:Why you should never use Socket.IO
by boylove142 on Tuesday November 08, 2016 @11:55PM
(#12906160)
Can I have opinions from someone who have already used this?
[ Parent
| on HN ]
Re:Why you should never use Socket.IO
by trakout on Wednesday November 09, 2016 @12:26AM
(#12906328)
Sure. The only thing SocketIO really has going for it is built-in support for falling back to long polling (for browsers that don't support websockets). That said, if you're using socketIO in production, you'll have to deal with memory leaks that aren't your fault (eg. even if you stick to boilerplate code). If you just want something quick and easy for a hackathon or personal project that you never want to scale, go for it. Otherwise be prepared for a rewrite, or increased hardware costs.
Re:Why you should never use Socket.IO
by diegorbaquero on Wednesday November 09, 2016 @12:32AM
(#12906364)
I'm the one proposing the switch in WebTorrent, you can read about the decision here: https://medium.com/@diegorbaquero/%C2%B5ws-as-your-next-webs...
I use it in production (BTorrent tracker) with 700-1300 peers active 24/7. 50MB or less RAM usage.