←back to thread

Pikaday: A friendly guide to front-end date pickers

(pikaday.dbushell.com)
287 points mnemonet | 1 comments | 11 Nov 25 14:58 UTC | HN request time: 0.207s | source
Show context
kmoser ◴[11 Nov 25 18:44 UTC] No.45891157[source]▶
> Travel booking often has a fixed schedule with limited time options, such as every 15 minutes. Relative dates like “Today” and “Tomorrow” can be easier to understand.

Except when you're booking a flight and you're not sure whether "today" is based on your local time, the server's local time, or GMT. (I often book flights right about midnight and find words like "today" and "tomorrow" to be completely confusing.)

replies(4): >>45891350 #>>45893047 #>>45893275 #>>45895437 #
1. jandrese ◴[11 Nov 25 21:21 UTC] No.45893047[source]▶
> Relative dates like “Today” and “Tomorrow” can be easier to understand.

This is one of those ideas that sounds like a good idea on paper, but can be an actual nightmare to implement. There are so many edge cases that can occur that you need to think about, especially once you get into cases like "this time next month". What if daylight savings time trips? What about time zones? What if it is January 31st and you want something a month from now? What if it is 12:05 at night and someone asks for 4PM tomorrow?

You should think long and hard before offering relative time options in program.