News for hackers. Stuff that matters.
Re:Why you should never use Socket.IO by Sacho on Wednesday November 09, 2016 @12:41AM (#12906429)
I like the library but the title is pure clickbait. I expected an article arguing this position, not a github repo. The github repo simply does not explain why "you should never use Socket.IO" - performance is not necessarily the only feature Socket.IO offers, it could be API surface, etc..Socket.IO is also two parts - a client and a server, and this library is just a server.

The title is doubly worse because it doesn't actually promote the library. You could quote the repo instead - "mWebSockets - a lightweight, efficient & scalable WebSocket server"

Re:Why you should never use Socket.IO by alexhultman on Wednesday November 09, 2016 @02:49AM (#12907368)
You don't consider a 60x performance overhead reason enough? And yeah, thanks so very much for flagging this post!
Re:Why you should never use Socket.IO by evv on Wednesday November 09, 2016 @11:54AM (#12911899)
If there is a 60x performance difference, why not put that information in the title? The title doesn't even mention uWebSockets, and it is clearly your intention to promote it. In the future, please avoid using link-baity titles like this on HN.

The reason I've selected socket.io for projects in the past is because of the awesome documentation and slick marketing, not because of snarky attacks on other libraries.

Re:Why you should never use Socket.IO by Sacho on Wednesday November 09, 2016 @02:53AM (#12907401)
I didn't flag the post.