Skip to main content
7 events
when toggle format what by license comment
Aug 1, 2018 at 20:18 audit First posts
Aug 1, 2018 at 20:19
Jul 18, 2018 at 13:18 comment added Brandin @DavidHammen This is a usability issue and it depends on how precise you need to be. When you want to know at least down to the hour, I would not think "yesterday" is good. "24 hours ago" is much clearer and is a commonly used human expression to emphasize the number of hours. Computers that are trying to be "human friendly" almost always get this wrong and over-generalize it to "yesterday" which is too vague. But to know this you'll need to interview users to see what they think. For some things you really want the exact date and time, so "yesterday" is always wrong.
Jul 17, 2018 at 11:59 comment added David Hammen A problem remains even with this refactorization, which is that "yesterday" doesn't make much sense in the very wee hours of the morning (shortly after 12:01 AM). In human friendly terms, something that happened at 11:59 PM doesn't suddenly change from "today" to "yesterday" when the clock slips past midnight. It instead changes from "1 minute ago" to "2 minutes ago". "Today" is too coarse in terms of something that happened but minutes ago, and "yesterday" is fraught with problems to night owls.
Jul 17, 2018 at 8:01 comment added Hulk @Deduplicator sure, but then depending on which languages/cultures you target, you might get away with only modifying pluralize using num and unit to build a key of some kind to pull a format string from some table/resource file. OR you might need a complete rewrite of the logic, because you need different units ;-)
Jul 16, 2018 at 16:15 comment added Deduplicator Next step is to internationalize, and there pluralize only working for a subset of english words will be a liability.
Jul 15, 2018 at 9:41 vote accept Arseni Mourzenko
Jul 13, 2018 at 5:28 history answered Karl Bielefeldt CC BY-SA 4.0