I'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.
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.