News for hackers. Stuff that matters.
Re:It Isn’t Your Father’s Realtime Anymore: The Misuse of a ... by derefr on Sunday August 23, 2015 @03:25PM (#10106470)
From the business analytics example, I think a useful layman's definition of "realtime" might be able to be extracted: "fast enough that, given the speed of the task the client is trying to accomplish, the client is never blocked waiting on the computation in such a way that it then performs suboptinally against its deadlines."

In machine-assisted translation, "realtime" is whatever speed (milliseconds) is fast enough to have a conversation without pausing. In business, "realtime" is whatever speed (minutes/hours) is fast enough that the feed of information outpaces your ability to absorb and change strategy in response to the information.

Interestingly, VR technology is "realtime" by both definitions: any perceptible latency (layman's definition) is unacceptable and causes feelings of "VR sickness"—so hard limits on frame delivery (technical definition) must be set. Or, "VR must be hard realtime in order to be realtime."

Re:It Isn’t Your Father’s Realtime Anymore: The Misuse of a ... by nickpsecurity on Sunday August 23, 2015 @11:41PM (#10107797)
"I think a useful layman's definition of "realtime" might be able to be extracted: "fast enough that, given the speed of the task the client is trying to accomplish, the client is never blocked waiting on the computation in such a way that it then performs suboptinally against its deadlines.""

That's actually a reasonable definition that could lead to re-interpretation and new usage by lay people. VR is a good example. Matter of fact, we did use that in game design because we had to differentiate between what had no delay and the pre-rendered graphics used in cut-scenes. We normally just said gameplay footage but some said "rendered in real-time." Those using VRML (the "VWWW") on dial-up knew what the opposite of real-time was. ;)