Real-time means something specific: every operation has a hard limit for upper bounded time.
I'm working on an embedded system right now; they typically cannot use garbage collection, because any GC pauses will utterly destroy the project's real-time guarantees. This board's microprocessor has an external hardware watchdog, which reboots the whole system unless I reset a timer every 2.5 msec or less. This is a reasonable limit, because if the program is unresponsive for too long, people may die. (It's automotive hardware.)
I think calling anything running in Javascript and across a network "real-time" is a bit misleading. What you mean is "soft real-time", which is far more forgiving.
I'm working on an embedded system right now; they typically cannot use garbage collection, because any GC pauses will utterly destroy the project's real-time guarantees. This board's microprocessor has an external hardware watchdog, which reboots the whole system unless I reset a timer every 2.5 msec or less. This is a reasonable limit, because if the program is unresponsive for too long, people may die. (It's automotive hardware.)
I think calling anything running in Javascript and across a network "real-time" is a bit misleading. What you mean is "soft real-time", which is far more forgiving.