What is wrong with Nasa mission to Mars? could it be Java?...
Thanks to Carl Franklin (.Net Rocks!), I now know that Nasa has been using Java for their Spirit rover mission to Mars ...
Having been a J2EE guy until I was hit by the CLR truck (back in the early days of 1st beta), I am not keen on trashing Java (do you easily trash your older loves?), but I just can't fight it...
Well, the story about the Mars mission goes like this (excerpts from MSNBC):
"NASA hoped communication with the six-wheeled rover would resume Friday morning after two days without receiving any significant data "
"Since Wednesday, its 19th day on Mars, the Spirit has sent back to Earth only meaningless radio noise or simple beeps acknowledging receipt of commands"
"Among the possible causes: a corruption of its software or computer memory. If the software is awry, NASA can fix it from Earth by beaming patches across more than 100 million miles of space or by rebooting the rover’s computer. But if the problem lies with the rover’s hardware, the situation would be far more grave — perhaps beyond repair"
"Preliminary indications suggested the rover’s radio was working, and it continued to generate power from the sun with its solar panels. Spirit’s internal clock also was running and had roused the rover several times on cue."
"Initially, engineers believed bad weather on Earth — a thunderstorm near a Deep Space Network antenna in Australia — had caused the communications glitch. But weather was later discounted as the source"
Well, sounds like software is the the cause, and it is java stuff ... Could that be the cause? some IIOP ORB not doing it right (sounds like déja vu, doesn't it?)
You would think they know better, haven't they heard of .Net?
The credits of the idea of this entry goes to Carl (on IM, here is how he displayed his name : "Carl Franklin - NASA should've used .Net")
main
2/8/2004 9:51:11 PM UTC
|