Norbert Lindenberg (2013-07-17T23:50:42.000Z)
On Jul 17, 2013, at 13:58 , Brendan Eich <brendan at mozilla.com> wrote:

> No, *time* is stored as milliseconds after the epoch in a number (IEEE double).
> 
> A Date object includes position on planet and timezone politics (see getTimezoneOffset).

No, it doesn't. Any time zone information used by getTimeZoneOffset and other non-UTC Date API is based on time zone information in the environment: the "local time zone" is typically what the user has told the OS to use. A Date object itself only wraps the time value.

Norbert
domenic at domenicdenicola.com (2013-07-24T00:44:21.782Z)
On Jul 17, 2013, at 13:58 , Brendan Eich <brendan at mozilla.com> wrote:

> No, *time* is stored as milliseconds after the epoch in a number (IEEE double).
> 
> A Date object includes position on planet and timezone politics (see getTimezoneOffset).

No, it doesn't. Any time zone information used by getTimeZoneOffset and other non-UTC Date API is based on time zone information in the environment: the "local time zone" is typically what the user has told the OS to use. A Date object itself only wraps the time value.