Operating with arbitrary timezones

[Alexander Jones]

Don't confuse timezones with timezone offsets. They are different concepts.

On Friday, 5 August 2016, Jon Zeppieri <zeppieri at gmail.com> wrote:

>
>
> On Fri, Aug 5, 2016 at 5:58 PM, Alexander Jones <alex at weej.com
> <javascript:_e(%7B%7D,'cvml','alex at weej.com');>> wrote:
>
>> What I meant by Date+Time components was actually { year, month, day,
>> hours, minutes, seconds, offset }. I think it makes sense to formalise this
>> as an expression of a time point (aka Date) *in a particular timezone*. For
>> example this can be used to decide e.g. "are these two time points in the
>> same month in this specific timezone", where that month may be e.g. 31 days
>> + 1 hour. It could also be formatted for display.
>>
>> Conflating Date projections into a timezone, with formatting, is a bit of
>> a conceptual error IMO. Convenient, but incorrect, as per Single
>> Responsibility Principle.
>>
>> Alex
>>
>>
> UTC offsets are terrible representations of time zones, because they don't
> acknowledge that many actual local timelines are discontinuous.
>
> When you don't need time zones, it's best to avoid them (and UTC offsets)
> altogether, but when you really need them, UTC offsets just aren't enough.
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20160805/9b21fe12/attachment.html>