I wanted to add WebSocket support in a node.js backend for a game I develop. This project has zero dependency outside node.js itself and I was reluctant to add any dependency for this, so I implemented WebSockets myself, with the help of a few example code and documentation from MDN. It does not handle the edge cases (that I don't need), but it's quite straightforward and I'm far from having Daniel's expertise in this kind of stuff.<p>I trust him to implement WebSockets correctly, it's way easier than most things he probably had to handle in curl.<p>It's good he went for a solution that does not bloat curl.<p>Good to see this feature in Curl too. libcurl is very nice, things are designed in a straightforward way and it's flexible, it's a library done with taste, and the curl program is also very helpful and being able to debug websocket related stuff with it might be very handy.<p>About:<p>> [libwebsockets] seems (too) tightly integrated with event libraries<p>I too often was slowed down by this kind of stuff when wanting to use anything on top of glib, like dbus for instance. These things want your program to be written in a certain way, rather than your program being able to call the library as it sees fit. In particular, you need to bent to the glib's event loop, and good luck if your program does not quite work like this. There are ways, but there are not very well documented.