Expected countdown error

[Dr J R Stockton]

For those of you with nothing better to de between the start of 2009 in
UTC and the start of 2009 in your local time (mainly Americans, I
expect), take a look at the bottom left-hand corner of
<http://saturn.jpl.nasa.gov/>, which currently (Dec 24th, 20:15 UTC
approx.) shows about 44d 12h.

I expect that an error of -366 days will appear in the West, and +365
days in the East, if they've not changed the relevant code (easily found
by View Source and read the beginning of function countdown) by then. I
did tell them about it in 2007, with a recent reminder. Let us hope
that Cassini itself was programmed by someone else.

 

[David Mark]

For those of you with nothing better to de between the start of 2009 in
UTC and the start of 2009 in your local time (mainly Americans, I
expect), take a look at the bottom left-hand corner of
<http://saturn.jpl.nasa.gov/>, which currently (Dec 24th, 20:15 UTC
approx.) shows about 44d 12h.

What a crock of shit that page is. Bad markup + YUI + more browser
sniffing + Flash and it breaks completely with scripting disabled
(it's no great shakes with it enabled either.) And how many times
have I heard "NASA uses them" as an excuse for relying on such
things. Are the outrageously bad results outweighed by the owner?

I expect that an error of -366 days will appear in the West, and +365
days in the East, if they've not changed the relevant code (easily found
by View Source and read the beginning of function countdown) by then. I

So did they change it or not? I don't care to watch their countdown.

did tell them about it in 2007, with a recent reminder. Let us hope
that Cassini itself was programmed by someone else.

Here's hoping there is no Javascript involved.

[snip]

 

[David Mark]

Damn you Mike Griffin, damn you!

Who? Google's description of the the first related result is:

"Apr 14, 2005 ... There's a problem with your browser or settings.
Your browser or your browser's settings are not supported. To get the
best experience ..."

And of course, it is a NASA page. Their Web developers are brain-
dead. I certainly hope these guys aren't involved with any of the
moving parts.

This is all your fault, isn't it?
ISN'T IT?!

Why don't you send him an email. He will likely get the message
faster.

[snip]

 

[Dr J R Stockton]

In comp.lang.javascript message <dc8c19ae-adcb-4fb9-8c9b-5d8f43dd5689@r2
8g2000vbp.googlegroups.com>, Wed, 24 Dec 2008 20:30:45, David Mark

And of course, it is a NASA page. Their Web developers are brain-
dead. I certainly hope these guys aren't involved with any of the
moving parts.

They had not fixed it. The Western error was partly caught; it said
that the event, whose date was given above as Feb 07 2009 (SCET), had
passed. In the East it showed about 400 days to go to that date.

It remains unfixed - and all that is needed is to insert the characters
UTC in the obvious place.