3 ms·
I disagree. Delta time requires less computational load on the brain. You rarely need to process the precise dates. If the article or item is old, "years" is t
by echelon 3y ago
I disagree. Delta time requires less computational load on the brain.
You rarely need to process the precise dates. If the article or item is old, "years" is the perfect measure. You very rarely need to consider the precise day the thing was created on.
Most tools should simply show the date as a tooltip. I was just sharing this video [1] on another thread, and YouTube does it perfectly. Date shows up on hover.
If you're presenting records in a tabular format, then dates win. But consumer products are enhanced by relative time.
[1] https://www.youtube.com/watch?v=WqZLkzdNYuI https://www.youtube.com/watch?v=WqZLkzdNYuI
- mvdtnz 3y agoHow do I hover on mobile?
- owenpalmer 3y ago> Delta time requires less computational load on the brain. I highly disagree. A quick glance at an absolute date immediately gives me the general idea of when it happened. Most of the time I want to know the exact date to compare it to other dates. When I see a relative date, I almost always need to subtract it.
- microflash 3y agoMaybe. Usually, relatively recent deltas are great which is mentioned in the article. They are less ambiguous enough to be helpful. But longer the deltas are from NOW, the higher is the cognitive overhead in my experience. And interfaces should reduce the overhead to make life easier for people.
- makeitdouble 3y agoThe main issue to me is the asymmetry on how much it really matters when date need to be precise, vs how how little it matters the rest of the time. Putting the spotlight on the format optimized for the people who care the less feels odd. There's not much load on the brain if we just skip the info we don't care about.
- Dylan16807 3y ago> YouTube does it perfectly. Date shows up on hover. You have to go to the video itself to get that tooltip, and the relative date is unreasonably vague a lot of the time. It's far from perfect.
- saltcured 3y agoI'm surprised nobody in the comments (that I can find) has mentioned another problem of relative times: am I the only one who considers of the ambiguity of _when_ was the page rendered and therefore what is the reference point for the relative time? Also, to be honest, I hate seeing times without timezone info. As someone often scheduling with people far away, it does not help me to have the calendaring tools silently convert times into my local timezone and display them unqualified. Particularly when everything tends towards a flat rendering style where it isn't always clear what is metadata from the system and what might be text written by the human far away. Generally, I dislike when designs fixate on "simple" and blithely ignore real failure modes. I have to try to get into some weird headspace to imagine how the UX designers failed at their job so I can try to predict the right failure mode and recover what I can out of the tools... Times are not universal. Displays are not always rendered at the moment the user observes them. Location of the observer is not always well known. Things fail. Doubly so with mobile.
- calfuris 3y agoI would actually point to YouTube as a bad example. YouTube refuses to make the absolute timestamp available unless you actually navigate to a particular video's page. That makes it impossible to see which video uploaded "X period ago" is more recent from e.g. a search result page. Even if you don't _usually_ want an absolute timestamp, there's no reason to make it completely inaccessible in most places.