3 ms·

most applications don't need to schedule events into the future though and its a smart strategy if all you need to worry about is the past

• masklinn 8y ago
  For very specific cases? Sure, but none of the comments talking about UTC everywhere cares to specify this rather important bit. Unless restrictions are specified I will assume we're talking about the general case, and for the general case it's just plain wrong.
  • y4mi 8y ago
    from my point of few its the other way around. There are very few applications that need to schedule events into the future, and that is literally the only situation where you have to worry about the timezone. Btw, keeping the timezone is insufficient as well if you're building a calendar/scheduler. If the user changes the timezone after scheduling the event... do you keep to the old one and alert him whenever, or do you adjust? There are a lot of edge cases with schedulers -- yet as i said before, most applications don't schedule into the future. They're mostly just doing things right now or within the next few minutes and keeping a log of their actions.
    • masklinn 8y ago
      > from my point of few its the other way around. > There are very few applications that need to schedule events into the future, and that is literally the only situation where you have to worry about the timezone. My experience is the exact opposite: there are few applications which only store past dates, and in those said date is usually indicative/barely even relevant and could just as well be part of a freeform comment or removed entirely.