Tuesday, 4 September 2007

GPhone Cometh


It finally looks like Google's GPhone might be a reality sometime soon. The Wall Street Journal carried an article on this last month, brushing away this long rumor and replacing this as fact, or perhaps making this a stronger longer rumor - depends on how you look at it.

Sure, if the product is coming out of Google, its definitely going to be desirable. However, whats interesting to note here, is who Google expects to pay for the calls you make using the GPhone. According to a source on Pocket-lint, they may be free, just like everything else Google offers...

"Google even envisions a phone service one day that is free of monthly subscription charges and supported entirely through ad revenue"

In other words, the price of using the GPhone could just be a minor invasion of privacy - a little like GMail.

According to reports on the internet, the GPhone could be available early next year. So if you were planning to get one for this Diwali, it might be more worthwhile to opt for a Nokia instead. I'm told their BL-5C equipped handsets are quite a blast, and you could end up saving a fortune on Diwali firecrackers too.

10 Questions and Answers About Google Phone (aka GPhone)

Monday, 3 September 2007

Software errors: A crash course

Just how much damage can a small software error do?

The costliest software error till date was the explosion of the unmanned Ariane 5 rocket about 37 seconds after lift-off on the morning of June 4, 1996.

This was its maiden flight, and the rocket was carrying 4 uninsured payloads worth about US$370 million. The mission critical Ariane 5 project itself took 10 years to develop at the cost of a whopping US$7 billion.

Apparently, it was blind software reuse that caused the problem, and sticking to the old "if it ain't broke, don't fix it" syndrome. An excerpt from a study on evolutionary design by the US Department of Homeland Security explains it well.

"The Ariane 5’s flight control software reused design specifications and code from its highly successful predecessor, the Ariane 4 launch vehicle. In particular, one of the on-board modules, the Inertial Reference System, performed a data conversion of a 64-bit floating point value related to the horizontal velocity of the rocket and attempted to place the result into a 16-bit signed integer variable. This computation had never caused a problem with the Ariane 4, but the more aggressive flight path and much faster acceleration of the Ariane 5 produced a higher horizontal velocity and a corresponding data value that was too large for the 16-bit signed integer variable, causing an arithmetic overflow. A redundant backup process used the same software and failed in the same manner. The Inertial Reference System then generated some diagnostic output that was incorrectly interpreted as flight control data by other portions of the flight control system. Based on this faulty interpretation, the flight control system took actions that led to the self-destruction of the rocket."

Wired has a list of 'History's worst software bugs' here.