Expected countdown error

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.

--
(c) John Stockton, nr London, UK. Turnpike v6.05.
Web URL:http://www.merlyn.demon.co.uk/ - w. FAQish topics, links, acronyms
PAS EXE etc : URL:http://www.merlyn.demon.co.uk/programs/ - see 00index.htm
Dates - miscdate.htm moredate.htm js-dates.htm pas-time.htm critdate.htm etc.

Dr J R Stockton wrote:
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 **** 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 wrote:

What a crock of **** 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?


"My name...Jose Jimenez."
"Is that NASA page done in 'crash code' Mr. Jimanez?"
"Oh...I hope not." :-)

Pat

Dr J R Stockton wrote:
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.


Damn you Mike Griffin, damn you!
This is all your fault, isn't it?
ISN'T IT?!
Don't wait for the translation into binary code...
"01000100 01100001" or "01101110 01111001 01100101 01110100"?
I thought so...

Pat

On Dec 24, 11:20*pm, Pat Flannery wrote:
Dr J R Stockton wrote:

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.

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]

David Mark wrote:

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


Anything wrong with NASA prior to the election is Griffin's fault;
anything afterward is Obama's fault.
That's the way I see it.
But I've never been one of those fans of the drive-by media, and know
that whatever the problem is, it can be solved by getting really
****ed-off at someone and bitching day-and-night about them.
I imagine that as a member of the chattering class, you don't agree with
that, do you, Mr. Commie?
That's why you cut this vital part of my posting:

Don't wait for the translation into binary code...
"01000100 01100001" or "01101110 01111001 01100101 01110100"?
I thought so...

Well, we real true-blue Americans will not tolerate that sort of **** on
the night Our Savior was born to save us from Marxist atheism and showed
us the way to be followers of The Prince Of Peace - via a worldwide war
of extermination against anyone who disagrees with us.
Few know that after Jesus reattached the Roman soldier's ear after the
Apostle Peter cut it off, He promptly pulled out a Desert Eagle .50
caliber pistol and blew the *******'s brains all the way to Damascus.
Of course, you don't read _that_ in the gospels, do you?
You know why?
That Antichrist Pope in Rome, that's why!
Typical commie rewriting of history! :-D

Pat

In comp.lang.javascript message dc8c19ae-adcb-4fb9-8c9b-5d8f43dd5689@r2
8g2000vbp.googlegroups.com, Wed, 24 Dec 2008 20:30:45, David Mark
posted:
Dr J R Stockton wrote:

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.

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.

--
(c) John Stockton, Surrey, UK. Turnpike v6.05 MIME.
Web URL:http://www.merlyn.demon.co.uk/ - FAQish topics, acronyms, & links.
Proper = 4-line sig. separator as above, a line exactly "-- " (SonOfRFC1036)
Do not Mail News to me. Before a reply, quote with "" or " " (SonOfRFC1036)