3 ms·
agree with your point, but i don't see any performance comparisons, at the end of the day, i'm looking at performance and stability as a leading factor for why
by epynonymous 7y ago
agree with your point, but i don't see any performance comparisons, at the end of the day, i'm looking at performance and stability as a leading factor for why i choose a particular library over another. obviously there are other factors like documentation, how well a library is maintained (i.e. any checkins in the last few weeks because there are bound to be bugs), popularity (i.e. github stars), and generally the interface of the library, is it methodical or cumbersome?
- nhooyr 7y agoI updated the comparison, I think you'll find it more compelling in terms of stability and performance. To summarize, they're about equal in terms of performance but I'd argue my library wins on stability and maintainability as the minimal API enables a tiny codebase, which means less docs, less tests and most importantly, less bugs. Furthermore, the future of gorilla/websocket is uncertain. https://github.com/gorilla/websocket/issues/370 https://github.com/gorilla/websocket/issues/370 https://github.com/nhooyr/websocket#gorillawebsocket https://github.com/nhooyr/websocket#gorillawebsocket