I don't normally like bashing open-source projects, but socket.io should not be used.
I don't normally like bashing open-source projects, but socket.io should not be used. It may be noob-friendly, but that's just because it does things so automatically that you can't really use it correctly. When I was a websockets noob, I used socket.io briefly, and it was a complete waste of time. See, for example, https://github.com/Automattic/socket.io-client/issues/572 (closed without comment). If you want a nice websockets library that handles old browsers, use SockJS. It's far better. [edit: fixed a silly typo]
Posted by amluto on Apr 13, 2015, 11:45 PM
Tags
Related issues
- That isn't really relevant for the tool starting the container.
- Why is there no link to the source?
- Something I wonder about in this domain is if this is the fault of the language.
- Namespace pollution is an annoying problem in Rust.
- Currently, no language ports of Timefold Solver are planned.
- I agree with you, almost all .NET code I write is within the .NET framework, yet when I look at C# repos, it's disheartening to see so ma...
Raise real-world problems, find people facing the same issue, and discuss solutions.7,000 issues0 comments
hackernews (Software)
That isn't really relevant for the tool starting the container.
Why is there no link to the source?
Something I wonder about in this domain is if this is the fault of the language.
Namespace pollution is an annoying problem in Rust.
Currently, no language ports of Timefold Solver are planned.
I agree with you, almost all .NET code I write is within the .NET framework, yet when I look at C# repos, it's disheartening to see so ma...
Why is there no simple workaround for this?
I have been using https://github.com/jacktasia/dumb-jump to quickly jump to definitions.
I don't normally like bashing open-source projects, but socket.io should not be used.
I don't normally like bashing open-source projects, but socket.io should not be used. It may be noob-friendly, but that's just because it does things so automatically that you can't really use it correctly. When I was a websockets noob, I used socket.io briefly, and it was a complete waste of time. See, for example, https://github.com/Automattic/socket.io-client/issues/572 (closed without comment). If you want a nice websockets library that handles old browsers, use SockJS. It's far better. [edit: fixed a silly typo]
Comments (0)
No comments yet. Start the discussion.