2 ms·
It's not overengineering. It's easier to deal with times with timezones (probably converting them back to epoch time, but doing so unambiguously). If you've nev
by jerf 17y ago
It's not overengineering. It's easier to deal with times with timezones (probably converting them back to epoch time, but doing so unambiguously). If you've never done date handling correctly before, you may not realize that. It only takes one place where the ambiguity bites you to make up for all the "ease" you got yourself by leaving them off, and you point out the case where the user doesn't even have to change timezones: DST. It doesn't hardly add any lines of code to get it right.
It's really no different than arguing "I don't need to know about text encodings"; it's actually easier to do it right the first time than just muddle along. Text encodings and dates are hard because people just muddle along and think they're getting somewhere. Fortunately, it's a lot easier to seal away the pain with datetimes than it is with text encodings.