Socket.io: Socket.io is not a realtime implementation of sockets. Evidence attached

[samcv]

Note: for support questions, please use one of these channels: stackoverflow or slack

You want to:

• [x] report a bug
• [ ] request a feature

Current behaviour

“In computer science, real-time computing (RTC), or reactive computing describes hardware and software systems subject to a "real-time constraint", for example from event to system response. Real-time programs must guarantee response within specified time constraints, often referred to as "deadlines" .” Source

socket.io does not meet this criteria

Steps to reproduce (if the current behaviour is a bug)

• Read definition of realtime computing
• Read socket.io site which says: "FEATURING THE FASTEST AND MOST RELIABLE REAL-TIME ENGINE"
• Use socket.io
• See screenshot attached

Expected behaviour

Expected a real time implementation of sockets.

Setup

• OS: linux
• browser: chrome
• socket.io version: all of them

Other information (e.g. stacktraces, related issues, suggestions how to fix)

Further evidence by this screenshot

[dndteam]

@samcv You must be fun at parties ...

[jamesshore]

Please don't waste maintainers' time with this kind of crap. Socket.IO is a tool for real-time web, not real-time computing. Like it or not, language evolves. (And even though it doesn't have to, the term "real-time web" does make sense as an example of soft real-time computing where the time constraint is on the order of 1-10s.)

(not a Socket.IO maintainer)