- 3.2k
- 2
- 35
- 67
I’m going to provide an argument against using Socket.IO.
I think using Socket.IO solely because it has fallbacks isn’t a good idea. Let Internet Explorer 8 RIP.
In the past, there have been many cases where new versions of Node.js has broken Socket.IO. You can check these lists for examples... https://github.com/socketio/socket.io/issues?q=install+error
If you go to develop an Android app or something that needs to work with your existing app, you would probably be okay working with WS right away, Socket.IO might give you some trouble there...
Plus the WS module for Node.js is amazingly simple to use.
I’m going to provide an argument against using Socket.IO.
I think using Socket.IO solely because it has isn’t a good idea. Let Internet Explorer 8 RIP.
In the past, there have been many cases where new versions of Node.js has broken Socket.IO. You can check these lists for examples... https://github.com/socketio/socket.io/issues?q=install+error
If you go to develop an Android app or something that needs to work with your existing app, you would probably be okay working with WS right away, Socket.IO might give you some trouble there...
Plus the WS module for Node.js is amazingly simple to use.
I’m going to provide an argument against using Socket.IO.
I think using Socket.IO solely because it has fallbacks isn’t a good idea. Let Internet Explorer 8 RIP.
In the past, there have been many cases where new versions of Node.js has broken Socket.IO. You can check these lists for examples... https://github.com/socketio/socket.io/issues?q=install+error
If you go to develop an Android app or something that needs to work with your existing app, you would probably be okay working with WS right away, Socket.IO might give you some trouble there...
Plus the WS module for Node.js is amazingly simple to use.
- 31.3k
- 22
- 110
- 134
ImI’m going to provide an argument against using socketSocket.ioIO.
I think using socketSocket.ioIO solely because it has fallbacks isntisn’t a good idea. Let IE8Internet Explorer 8 RIP.
In the past, there have been many cases where new versions of NodeJSNode.js has broken socketSocket.ioIO. You can check these lists for examples... https://github.com/socketio/socket.io/issues?q=install+error
If you go to develop an Android app or something that needs to work with your existing app, you would probably be okay working with WS right away, socketSocket.ioIO might give you some trouble there...
Plus the WS module for Node.JSjs is amazingly simple to use.
Im going to provide an argument against using socket.io.
I think using socket.io solely because it has fallbacks isnt a good idea. Let IE8 RIP.
In the past there have been many cases where new versions of NodeJS has broken socket.io. You can check these lists for examples... https://github.com/socketio/socket.io/issues?q=install+error
If you go to develop an Android app or something that needs to work with your existing app, you would probably be okay working with WS right away, socket.io might give you some trouble there...
Plus the WS module for Node.JS is amazingly simple to use.
I’m going to provide an argument against using Socket.IO.
I think using Socket.IO solely because it has isn’t a good idea. Let Internet Explorer 8 RIP.
In the past, there have been many cases where new versions of Node.js has broken Socket.IO. You can check these lists for examples... https://github.com/socketio/socket.io/issues?q=install+error
If you go to develop an Android app or something that needs to work with your existing app, you would probably be okay working with WS right away, Socket.IO might give you some trouble there...
Plus the WS module for Node.js is amazingly simple to use.
- 2.4k
- 26
- 42
Im going to provide an argument against using socket.io.
I think using socket.io solely because it has fallbacks isnt a good idea. Let IE8 RIP.
In the past there have been many cases where new versions of NodeJS has broken Socketsocket.io. You can check these lists for examples... https://github.com/socketio/socket.io/issues?q=install+error
If you go to develop an Android app or something that needs to work with your existing app, you would probably be okay working with WS right away, socket.io might give you some trouble there...
Plus the WS module for Node.JS is amazingly simple to use.
Im going to provide an argument against using socket.io.
I think using socket solely because it has fallbacks isnt a good idea. Let IE8 RIP.
In the past there have been many cases where new versions of NodeJS has broken Socket. You can check these lists for examples... https://github.com/socketio/socket.io/issues?q=install+error
If you go to develop an Android app or something that needs to work with your existing app, you would probably be okay working with WS right away, socket.io might give you some trouble there...
Plus the WS module for Node.JS is amazingly simple to use.
Im going to provide an argument against using socket.io.
I think using socket.io solely because it has fallbacks isnt a good idea. Let IE8 RIP.
In the past there have been many cases where new versions of NodeJS has broken socket.io. You can check these lists for examples... https://github.com/socketio/socket.io/issues?q=install+error
If you go to develop an Android app or something that needs to work with your existing app, you would probably be okay working with WS right away, socket.io might give you some trouble there...
Plus the WS module for Node.JS is amazingly simple to use.