3 ms·

Real Time. Over the internet. What. I actually looked it up. https://en.wikipedia.org/wiki/Real-time_web https://en.wikipedia.org/wiki/Real-time_web It feels

Real Time. Over the internet. What. I actually looked it up. https://en.wikipedia.org/wiki/Real-time_web https://en.wikipedia.org/wiki/Real-time_web It feels like something a SW company wrote up for the sole purpose of making up the idea. The "Difference from real-time computing" is uncited. Hell the entire thing is uncited except for Real Time search, from Google.

skrebbel 6y ago
Are you complaining about some shitty Wikipedia article because an Uber article uses the same term "Real-time"? How is that related?
- dahfizz 6y ago
  The problem is that "real time" has a meaning. A real time system has bounded latency and can make guarantees about how long something will take. See stream reservation [1] as an example. The Uber system is not real time. It's entirely possible that every switch and router between you and the Uber server has it's buffers full. Round trip time is entirely unbounded over the internet. You could say their system is "fast" or "responsive", but "real time" is not a marketing buzz word, it has technical meaning. IDK why OP chose to link to that weird article to try and illuminate this point. [1] https://en.m.wikipedia.org/wiki/Stream_Reservation_Protocol https://en.m.wikipedia.org/wiki/Stream_Reservation_Protocol
  - atonse 6y ago
    I think it’s probably not worth having this debate because nowadays, unless you’re actually talking about a valid context (like a rocket engine), the use of the term more often means “soft realtime” which is, “pushed out across systems when it occurs, not as part of a periodic batch process”
  - ofrzeta 6y ago
    I think it's obvious that "real-time" has different meanings in different contexts. Besides operating systems we also have the "Real-Time Transport Protocol" (RTP) which has different timing constraints than an real-time OS.
  - skrebbel 6y ago
    That's the common meaning of "real time" in embedded system land, correct. In web land, it tends to mean "if a user makes a change here, it auto updates on some other user's screen there without either user clicking 'save' or 'refresh' or something like that". Both are clear definitions in widespread use, and it's obvious that the Uber people mean the latter. Your comment is like complaining that people writing a cryptocurrency blog use the word "crypto" wrong because obviously it means cryptography.
  - danpalmer 6y ago
    Does knowing that your driver is about to collect you not have a bounded latency? Given the necessary UX and the fact that Uber charges you if you don’t turn up for the ride, I’d say this absolutely has a bounded latency defined in their charging policy. Real-time systems can have any bounded latency, it doesn’t have to be “fast”. I’d say Uber probably have a few hard-real-time systems around 5 minutes of latency, and a lot of soft-real-time systems around the latency of either 15-30s or around the duration of an Uber ride.

skrebbel 6y ago

Are you complaining about some shitty Wikipedia article because an Uber article uses the same term "Real-time"? How is that related?

dahfizz 6y ago
The problem is that "real time" has a meaning. A real time system has bounded latency and can make guarantees about how long something will take. See stream reservation [1] as an example. The Uber system is not real time. It's entirely possible that every switch and router between you and the Uber server has it's buffers full. Round trip time is entirely unbounded over the internet. You could say their system is "fast" or "responsive", but "real time" is not a marketing buzz word, it has technical meaning. IDK why OP chose to link to that weird article to try and illuminate this point. [1] https://en.m.wikipedia.org/wiki/Stream_Reservation_Protocol https://en.m.wikipedia.org/wiki/Stream_Reservation_Protocol
- atonse 6y ago
  I think it’s probably not worth having this debate because nowadays, unless you’re actually talking about a valid context (like a rocket engine), the use of the term more often means “soft realtime” which is, “pushed out across systems when it occurs, not as part of a periodic batch process”
- ofrzeta 6y ago
  I think it's obvious that "real-time" has different meanings in different contexts. Besides operating systems we also have the "Real-Time Transport Protocol" (RTP) which has different timing constraints than an real-time OS.
- skrebbel 6y ago
  That's the common meaning of "real time" in embedded system land, correct. In web land, it tends to mean "if a user makes a change here, it auto updates on some other user's screen there without either user clicking 'save' or 'refresh' or something like that". Both are clear definitions in widespread use, and it's obvious that the Uber people mean the latter. Your comment is like complaining that people writing a cryptocurrency blog use the word "crypto" wrong because obviously it means cryptography.
- danpalmer 6y ago
  Does knowing that your driver is about to collect you not have a bounded latency? Given the necessary UX and the fact that Uber charges you if you don’t turn up for the ride, I’d say this absolutely has a bounded latency defined in their charging policy. Real-time systems can have any bounded latency, it doesn’t have to be “fast”. I’d say Uber probably have a few hard-real-time systems around 5 minutes of latency, and a lot of soft-real-time systems around the latency of either 15-30s or around the duration of an Uber ride.