4 ms·

Node.js is the opposite of what some people would consider "real time." https://en.wikipedia.org/wiki/Real-time_computing https://en.wikipedia.org/wiki/Real-ti

Node.js is the opposite of what some people would consider "real time." https://en.wikipedia.org/wiki/Real-time_computing https://en.wikipedia.org/wiki/Real-time_computing

aikah 7y ago
Unfortunately both "realtime" and "systems" have become buzzwords, void of their actual meaning. "Websocket" isn't real time of even close to it.
- claytongulick 7y ago
  Words take on different meanings in different contexts, and get adopted in different domains all the time - this is how language works. An example - "I'm going to ping Bob to see if he's available" There are innumerable others. Sure, this isn't "real-time" in the context of microcontrollers, and RTOS stuff, but in the web app context, I think it counts.
  - goatlover 7y ago
    Right, but it would be best to stick with accurate technical definitions when discussing technical issues.
  - deleted 7y ago
    [deleted]
- dkarl 7y ago
  What I've learned from years of working with product managers is that anything that is both faster than a day and faster than we've conditioned users to expect can be called "real time." If you switch from generating reports nightly to doing it every four hours, that's "real time reporting."
jjtheblunt 7y ago
Wanted to say the same thing, in my case thinking of Sun's ChorusOS and Solaris schedulers and definitions of realtime wrt bounded dispatch latency. I can't believe, even having been a v8 committer ten years ago, that node can make guarantees about response time to events, i.e., bounds on dispatch latency, that are super enthusiastic. I hope I learn there's more to be enthused about.
- jjtheblunt 7y ago
  From Sun's (thus, now Oracle's) documentation : https://docs.oracle.com/cd/E19455-01/806-4750/chap7rt-21297/index.html https://docs.oracle.com/cd/E19455-01/806-4750/chap7rt-21297/...
progre 7y ago
Maybe it means "not with the usual latancy of a REST app" in this context. In a prevoius life I did systems that ran on microcontrollers. Back then even having an OS would disqualify you from getting to claim "real time". Everything ran on the interrupts.
tluyben2 7y ago
When I saw the title, I saw this misery before me where recruiters serve up people like the author to companies looking for ‘realtime system engineers’ just because people put keywords on their linked in and have blog posts which look insightful etc. We all have our skills, but realtime system engineering is not an easy one. Replacing that with something websockets would be better imho.
seangrogg 7y ago
In all fairness, I've heard the use of "real time" applications with respect to chat (websockets) or video (WrbRTC). This is the first time I've been introduced to this definition of real-time computing. I'd be interested to see how many people are aware of this definition and why there appears to be such a divide in the first place.

Node.js is the opposite of what some people would consider "real time." https://en.wikipedia.org/wiki/Real-time_computing https://en.wikipedia.org/wiki/Real-time_computing

aikah 7y ago

Unfortunately both "realtime" and "systems" have become buzzwords, void of their actual meaning. "Websocket" isn't real time of even close to it.

claytongulick 7y ago
Words take on different meanings in different contexts, and get adopted in different domains all the time - this is how language works. An example - "I'm going to ping Bob to see if he's available" There are innumerable others. Sure, this isn't "real-time" in the context of microcontrollers, and RTOS stuff, but in the web app context, I think it counts.
- goatlover 7y ago
  Right, but it would be best to stick with accurate technical definitions when discussing technical issues.
- deleted 7y ago
  [deleted]
dkarl 7y ago
What I've learned from years of working with product managers is that anything that is both faster than a day and faster than we've conditioned users to expect can be called "real time." If you switch from generating reports nightly to doing it every four hours, that's "real time reporting."

jjtheblunt 7y ago

Wanted to say the same thing, in my case thinking of Sun's ChorusOS and Solaris schedulers and definitions of realtime wrt bounded dispatch latency. I can't believe, even having been a v8 committer ten years ago, that node can make guarantees about response time to events, i.e., bounds on dispatch latency, that are super enthusiastic. I hope I learn there's more to be enthused about.

jjtheblunt 7y ago
From Sun's (thus, now Oracle's) documentation : https://docs.oracle.com/cd/E19455-01/806-4750/chap7rt-21297/index.html https://docs.oracle.com/cd/E19455-01/806-4750/chap7rt-21297/...

progre 7y ago

Maybe it means "not with the usual latancy of a REST app" in this context. In a prevoius life I did systems that ran on microcontrollers. Back then even having an OS would disqualify you from getting to claim "real time". Everything ran on the interrupts.

tluyben2 7y ago

When I saw the title, I saw this misery before me where recruiters serve up people like the author to companies looking for ‘realtime system engineers’ just because people put keywords on their linked in and have blog posts which look insightful etc. We all have our skills, but realtime system engineering is not an easy one. Replacing that with something websockets would be better imho.

seangrogg 7y ago

In all fairness, I've heard the use of "real time" applications with respect to chat (websockets) or video (WrbRTC). This is the first time I've been introduced to this definition of real-time computing. I'd be interested to see how many people are aware of this definition and why there appears to be such a divide in the first place.