Re: GMT Date Format Anomaly
JRS: In article <crbrsq$lii$1$8 30fa79d@news.de mon.co.uk>, dated Mon, 3
Jan 2005 16:31:02, seen in news:comp.lang. javascript, Mark Preston
<usenet@nosourc e.co.uk> posted :[color=blue]
>Dr John Stockton wrote:[color=green]
>> JRS: In article <cr3g6r$h39$1$8 302bc10@news.de mon.co.uk>, dated Fri, 31
>> Dec 2004 12:22:24, seen in news:comp.lang. javascript, Mark Preston
>> <usenet@nosourc e.co.uk> posted :
>>[color=darkred]
>>>Dr John Stockton wrote:
>>>
>>>>The wise programmer will allow for getting either UTC or GMT (and know
>>>>that the two are not synonymous, and in principle neither is correct).
>>>>AFAIK, however, one need not expect utc or gmt.
>>>>
>>>
>>>The wise reader will also know that GMT and UTC are the same thing.
>>>Unfortunatel y, as we all know, wise readers are as rare as rocking-horse
>>>droppings. .. :)[/color]
>>
>> No, GMT and UTC are not the same thing, even apart from what I was
>> referring to, which is that a coder must allow for the possibility of
>> getting either string from a Date Object method.
>>[/color]
>Technically, you are correct. GMT is a standard-period time recording
>(that is, it counts how long the Earth takes to revolve) and is
>consequently "inaccurate " since nothing in this life is as simple as a
>spinning planet is assumed to be.[/color]
Approximately correct.
[color=blue]
>UTC, on the other hand, is a derived
>probabilisti c decay-rate measurement.[/color]
Total rubbish. It has nothing at all to do with decay rates. UTC is
based on the SI second, which is based on a precise transition of Cs-133
(see footnote [+] to my previous article), plus adjustments to make it
agree with one of the GMT-class time scales to within 0.9 seconds.
See my WWW site, and confirm by means of the links it contains; do not
trust amateur sources.
[color=blue]
>But, be honest, who really cares about the odd leap-second or so?[/color]
Quite a number of people care quite a lot - granted, only a minority
know, but many more could be affected if a mistake were made.
The important things for this group remain that (a) one can never be
really safe in assuming that a string generated by the javascript
processor will not include GMT where UTC might be expected, or /vice
versa/, (b) javascript knows nothing of leap seconds, and behaves
arithmetically as GMT does.
--
© John Stockton, Surrey, UK. *@merlyn.demon. co.uk / ??.Stockton@phy sics.org ©
Web <URL:http://www.merlyn.demo n.co.uk/> - FAQish topics, acronyms, & links.
Correct <= 4-line sig. separator as above, a line precisely "-- " (SoRFC1036)
Do not Mail News to me. Before a reply, quote with ">" or "> " (SoRFC1036)
JRS: In article <crbrsq$lii$1$8 30fa79d@news.de mon.co.uk>, dated Mon, 3
Jan 2005 16:31:02, seen in news:comp.lang. javascript, Mark Preston
<usenet@nosourc e.co.uk> posted :[color=blue]
>Dr John Stockton wrote:[color=green]
>> JRS: In article <cr3g6r$h39$1$8 302bc10@news.de mon.co.uk>, dated Fri, 31
>> Dec 2004 12:22:24, seen in news:comp.lang. javascript, Mark Preston
>> <usenet@nosourc e.co.uk> posted :
>>[color=darkred]
>>>Dr John Stockton wrote:
>>>
>>>>The wise programmer will allow for getting either UTC or GMT (and know
>>>>that the two are not synonymous, and in principle neither is correct).
>>>>AFAIK, however, one need not expect utc or gmt.
>>>>
>>>
>>>The wise reader will also know that GMT and UTC are the same thing.
>>>Unfortunatel y, as we all know, wise readers are as rare as rocking-horse
>>>droppings. .. :)[/color]
>>
>> No, GMT and UTC are not the same thing, even apart from what I was
>> referring to, which is that a coder must allow for the possibility of
>> getting either string from a Date Object method.
>>[/color]
>Technically, you are correct. GMT is a standard-period time recording
>(that is, it counts how long the Earth takes to revolve) and is
>consequently "inaccurate " since nothing in this life is as simple as a
>spinning planet is assumed to be.[/color]
Approximately correct.
[color=blue]
>UTC, on the other hand, is a derived
>probabilisti c decay-rate measurement.[/color]
Total rubbish. It has nothing at all to do with decay rates. UTC is
based on the SI second, which is based on a precise transition of Cs-133
(see footnote [+] to my previous article), plus adjustments to make it
agree with one of the GMT-class time scales to within 0.9 seconds.
See my WWW site, and confirm by means of the links it contains; do not
trust amateur sources.
[color=blue]
>But, be honest, who really cares about the odd leap-second or so?[/color]
Quite a number of people care quite a lot - granted, only a minority
know, but many more could be affected if a mistake were made.
The important things for this group remain that (a) one can never be
really safe in assuming that a string generated by the javascript
processor will not include GMT where UTC might be expected, or /vice
versa/, (b) javascript knows nothing of leap seconds, and behaves
arithmetically as GMT does.
--
© John Stockton, Surrey, UK. *@merlyn.demon. co.uk / ??.Stockton@phy sics.org ©
Web <URL:http://www.merlyn.demo n.co.uk/> - FAQish topics, acronyms, & links.
Correct <= 4-line sig. separator as above, a line precisely "-- " (SoRFC1036)
Do not Mail News to me. Before a reply, quote with ">" or "> " (SoRFC1036)
Comment