Hacker News Reader

Comment by wolverine876 | Hacker News Reader

Pretty neat, though natural language is famously ambiguous. From the example,

  tu today      -> 2024-03-16T12:56:41.905455Z
  tu tomorrow   -> 2024-03-17T12:56:41.905455Z

I interpret "today" as the time period between 00:00 and 23:59:59.999999, and tomorrow similarly.

View on HN

The classic example is 'next Saturday'. Is this the next Saturday (since today is Friday that would be tomorrow) or the Saturday of next week (i.e. eight days time).

And then you end up with needing a locale based week, since different cultures (e.g. US versus UK) use different days to start the week (Sunday/Monday)

> 'next Saturday'. Is this the next Saturday (since today is Friday that would be tomorrow) or the Saturday of next week (i.e. eight days time).

this is never ambiguous. "saturday" is the saturday of the current week, and "next saturday" is the saturday of the following week

> this is never ambiguous

What is that based on? Your personal perception is not evidence of wider ambiguity either way (and neither is mine).

What is “next monday” at saturday?

"Monday" is two days after, and "next Monday" is 9 days after

Your boss comes up to you and says "I need this by Tuesday" and then storms out of the room. You look down at your watch to confirm you're not crazy. Today is Tuesday. When does your boss need it by?

boss spoke incorrectly. boss should have said "next tuesday". what you're asking for is essentially AI, which is beyond the scope of this tool

Those examples had me puzzled. I would have expected "tu tomorrow" to be 00:00:00 of the next calendar day (converted to UTC), rather than "now + 24 hours". If I wanted a particular time (besides 00:00:00) on the next day, I'd like to be able to input something like "9 AM tomorrow" or "tomorrow +9h".

also depends if you mean "today in UTC" or "today in local time expressed as UTC". most people want the latter

Reply on news.ycombinator.com