Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

There's a difference between latency and delay.

If I "touch a.txt" then run "ls", and see "a.txt", I'd consider my filesystem realtime. There's no point in being pedantic about "but there's a 50ms delay when I hit enter after typing ls so it's not realtime!!!".

"Realtime virus outbreak" implies that the site is somehow automatically identifying where the virus is and updating it's stats, rather than waiting for a human to update it.



Since "implies that the site is somehow automatically identifying where the virus is" is obviously impossible with current tech & infrastructure, the next most "real-time" interpretation is that it has the most up-to-date data as it becomes available... which it basically does AFAIK, assuming it automatically pulls from its data sources, such as the WHO situation report feed.

What would you recommend calling it instead?


It's not impossible, most countries have digitized medical records. It wouldn't be technically difficult to automatically send out a ping to a centralized location when a new patient is diagnosed with novel coronovirus. Politically, on the other hand, it's not going to happen.


Just call it an "up-to-date" map that is often updated.


It is a real time map of data that has been reported.


I don't think that's the case, it is a map of data updated by an editor. The website in question doesn't seem to fetch data automatically as the sources are making it available.


In your example you (human) created a file and you can now request the content of that file (from your filesystem) at any point.

In the given example there's a tracker (updated by humans) and you can see the current state of the tracker at any time (from their database).

I'm not sure what the distinction is here if you consider one realtime and the other not.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: