3 ms·

I was curious too, since I'm generally fond of socket.io. I've written my own small library around bare WebSocket API, and there are many aspects to consider, l

I was curious too, since I'm generally fond of socket.io. I've written my own small library around bare WebSocket API, and there are many aspects to consider, like fallbacks and reconnection. In my opinion, socket.io provides a simple and smallish interface that takes care of most needs. Here's an article I found, with opinions on the good and the bad. https://dzone.com/articles/socketio-the-good-the-bad-and-the-ugly https://dzone.com/articles/socketio-the-good-the-bad-and-the... (2018)

kelnos 6y ago
The interface is nice (from Javascript; it's impossible to write something type-safe in any language where you like to care about type safety); the protocol and implementation itself is horrifying. Some of the protocol's handshaking gymnastics was necessary 15 years ago when you couldn't rely on there being a standards-conforming Websocket implementation, but those days are long gone. Documentation is sparse, and when you find some docs, half the time it isn't clear which (incompatible) version of the protocol they're talking about. Source: I was working on writing an interoperable server implementation of socket.io a couple years ago, and it was way more work than it should have been.