Conversation
Edited 9 months ago
Whoever thinks that getting cute by replacing precise timestamps with "1 hour ago", "3 weeks ago", "6 months ago", "recently" etc is a good idea:

STOP IT!

I am particularly glaring at you, github! I don't know if you did it first, but so many other people copied this blight on humanity from you.
3
13
0

@karinjiri You can usually hover and it will show you the actual datetime. Works for GitHub, mastodon, reddit, etc.

1
0
0
That's a pain in the rear. I could (maybe) forgive github if there was a setting or option so that it never, ever showed cute time approximations at all, but there isn't one.

It's far worse than just github etc though. It's a plague all over the place now, and it's bugging me right now in iOS. There's no mouse-over tooltip there to get details.

Why do I care at this particular moment? I just had an mDNS freakout and I want to know if the homepods just auto-updated. All that they say is it was "recent". Does that correspond to the 1:18am hiccup? I don't think so, but its impossible to tell.

If it was the homepods then that's fine, I can stop looking. If not, then something else has broken, perhaps the cross-vlan mDNS repeaters. Or unifi manager updates.

Anyway, I still think it's mostly github's fault for popularizing this. Is there somebody else I'm missing?
1
0
0

@karinjiri Reddit had it in 2005, years before GitHub was even a thing.

0
0
0
@karinjiri it's sick, agreed, but it is no nearly as bad as introduction of mibibytes and changing sizes as being ambiguous entities :-)
1
0
0
@jarkko @karinjiri I gotnso annoyed by people messing up with units that at least I'm using SI unit. File size is 1232 hbit. Some get it and others don't. But at least it's completely logical and correct unit.
1
0
0
Problems do not arise when let's say daemon logs "1024 MiB". Then can be quite safely assumed the aligment with ISO/IEC 80000-13.

However, if the same daemon emits "1024 MB" instead, I need to download the full source code and study it enough to be sure what is what.

Obviously this mess applies also to hardware.

It is a cardinal sin to break backwards compatibility just plain randomly. Should be dead obvious for any legit engineer that instead it would have been better to invent a new unit for base-1000 sizes, instead of corrupting base-1024 sizes.
0
0
1

@karinjiri I think Ruby on Rails did it first, or at least widely popularised it as a default, and GitHub always was (still is?) built with Rails.

1
0
0

@sanityinc @karinjiri Ruby on Rails is from 2004. That’s really recent when it comes to discussion forums and systems deriving from those forums.

The Swedish discussion forum type KOM, in use from 1978 (older than Usenet) and still in use today, uses relative time in most of its implementations. It’s however somewhat unclear if it did this from the beginning or not. All archives are dumped much later than the posts, so they would show full date anyway.

1
0
0

@ahltorp @karinjiri Interesting - thanks for sharing! I wonder if the Scandinavian heritage influenced DHH's choice in that regard. I don't remember seeing support for that style baked into any earlier framework.

0
0
0