The Cause and effect of Google’s driverless cars.

In case you haven’t been living under a rock, you must be aware of the Google’s Self-Driving Cars.

What was a starter project by Google for developing autonomous cars, the concept is now beyond the experimental stages and nearing its implementation.

In the US, these "self-driving” cars were first introduced in Nevada followed by Florida, the second state to allow autonomous cars on state roads, followed up by California.

Now UK is planning to allow driverless cars on public roads from 2015.

So all this seems like a pretty cool implementation of technology which is even publically accessible! But what are the effects of this cause?

‘Effects’ you may ask? Yes, there are effects here too.

Since safety is a prime focus and problem area these cars are aimed to tackle, there is the statistics of low mortality which will slowly be prevalent.

The MakerBot founder Bre Pettis said in his recent interview with Fortune, that

“…the take off of self-driving cars could lead us to more organ shortages than ever, since a major source of organ donations come from car accident victims.

We have this huge problem that we sort of don't talk about, that people die all the time from car accidents, Right now, our best supply of organs comes from car accidents. So, if you need an organ you just wait for somebody to have an accident, and then you get their organ and you're better."

Sounds gross? Yes, but sadly, that is the reality.

As per the current statistics - 

“30,000 people die in traffic collisions in the U.S. and 90% of U.S. auto collisions are blamed on human error, and 40% are the result of factors such as alcohol, drugs or fatigue. Therefore robotic cars, such as Google driverless Car, are designed to navigate roads and keep passengers safe.”

“So if there is less car deaths, organ donations would be adversely impacted. Then the 3D printed organ might be a solution. Although this is a dark way of looking at it, Griffith also agrees that Pettis has a point. Pettis pointed out that 3D printing organs will not be the focus of development until the self-driving technology causes the shortages.”

So here is the cause, and the effect, all clearly defined.

And unless the 3D organ printing becomes a viable and an effective solution, sadly the statistics for death by accidents and death due to lack of organ donations would eventually even out.

References: http://fortune.com/2014/08/15/if-driverless-cars-save-lives-where-will-we-get-organs/

Technorati Tags: Google,Driverless,carss,autonomous,3D print,organ,donation

The Cause and effect of Google’s driverless cars.

In case you haven’t been living under a rock, you must be aware of the Google’s Self-Driving Cars.

What was a starter project by Google for developing autonomous cars, the concept is now beyond the experimental stages and nearing its implementation.

In the US, these "self-driving” cars were first introduced in Nevada followed by Florida, the second state to allow autonomous cars on state roads, followed up by California.

Now UK is planning will allow driverless cars on public roads from 2015.

So all this seems like a pretty cool implementation of technology which is even publically accessible! But what are the effects of this cause?

‘Effects’ you may ask? Yes, there are effects here too.

Since safety is a prime focus and problem area these cars are aimed to tackle, there is the statistics of low mortality which will slowly be prevalent.

The MakerBot founder Bre Pettis said in his recent interview with Fortune, that

“…the take off of self-driving cars could lead us to more organ shortages than ever, since a major source of organ donations come from car accident victims.

We have this huge problem that we sort of don't talk about, that people die all the time from car accidents, Right now, our best supply of organs comes from car accidents. So, if you need an organ you just wait for somebody to have an accident, and then you get their organ and you're better."

Sounds gross? Yes, but sadly, that is the reality.

As per the current statistics - 

“30,000 people die in traffic collisions in the U.S. and 90% of U.S. auto collisions are blamed on human error, and 40% are the result of factors such as alcohol, drugs or fatigue. Therefore robotic cars, such as Google driverless Car, are designed to navigate roads and keep passengers safe.”

“So if there is less car deaths, organ donations would be adversely impacted. Then the 3D printed organ might be a solution. Although this is a dark way of looking at it, Griffith also agrees that Pettis has a point. Pettis pointed out that 3D printing organs will not be the focus of development until the self-driving technology causes the shortages.”

So here is the cause, and the effect, all clearly defined.

And unless the 3D organ printing becomes a viable and an effective solution, sadly the statistics for death by accidents and death due to lack of organ donations would eventually even out.

References: http://fortune.com/2014/08/15/if-driverless-cars-save-lives-where-will-we-get-organs/

Technorati Tags: Google,Driverless,carss,autonomous,3D print,organ,donation

Using MySQL / Java and getting the noAccessToProcedureBodies issue? Read on..

If you use much the MySQL + Java setup, you may have faced the ‘noAccessToProcedureBodies’ error while accessing stored procedures (mostly remotely).
The chances are that the procedure was created by another user (i.e. the DEFINER attribute), and the calling user is different.
I recently faced this issue in one of my projects, where-in we were trying to execute a remote DB’s stored procedure from a java application.
A common solution on the internet is to use the “noAccessToProcedureBodies=true” option in the JDBC connection string.
This seems to work for most of the people out there, but sadly didn’t work for us. What we tried then is another option called the “useInformationSchema=true”.
We removed the earlier option ‘noAccessToProcedureBodies’ option and added this in the JDBC string. This solution too eluded us, but then I tried upgrading the mysql-connector. We were using the mysql-connector-java-5.1.9 version which ideally should have worked (as we just needed a > 5.0.4 version for the solution)
But then I upgraded this to the mysql_connector_java_5.1.30 and this functionality started behaving as expected!
So, the end solution was to use the ‘useInformationSchema’ in the JDBC conn string and have the latest connector in place!
Technorati Tags: MySQL,Java,Issue,Read,error,procedures,setup,procedure,user,DEFINER,solution,option,JDBC,connection,version,noAccessToProcedureBodies,useInformationSchema,connector

Rapid Environment Editor – A must have for every developer using Windows OS!

If your development environment is Windows, Rapid Environment Editor is going to be your new favorite power user application.

This nifty little application is helpful in readily accessing the obscure to change OS environment variables.

It provides an easy to use GUI where-in you can boss around your Windows Environment with ease and with much more power than the small and “hard to understand” default environment editor.

The home URL is here.

The latest version RapidEE 8.x supports all versions of Windows, XP, 2003, Vista, 2008, Windows 7 & 8 and both 32 and 64-bit versions. It is also available as a portable download!

Technorati Tags: Rapid,environment,editor,windows,operating system,java,classpath,path,poweruser

This post has been compiled on my N9005!

posted from Bloggeroid

Modernizr - Detecting HTML5 and CSS3 features in client browser easily! <Part 2>

Continuing with the Modernizr series, we now start with the implementation.

So how to go about implementing these compatibility checks?

Until recently, we have been using many techniques for Browser Detection, the most common of which is to use JavaScript for getting information from the user-agent header.

Listing 1 provides us an idea about implementing the user-agent header check (a.k.a. UA sniffing).

   1: <script type="text/javascript">

   2: ieDetectionFunction(){

   3:   if ( navigator.userAgent.indexOf("MSIE") > 0 ) {

   4:     // Yes, we have IE, now do IE related stuff!

   5:   }

   6: }

   7: </script>

Listing 1: Function with user-agent header check

Though UA sniffing has been a standard practice, nevertheless it poses some issues. Considering the above example, we are faced with the inability to ascertain the exact ‘MSIE’ version in this case. Moreover, it also doesn’t provide any function specific checking.

For checking versions, the workaround is to use the navigator object in combination with regular expressions to detect the various browsers and their exact versions.

Specifically, we would query the navigator.appName and navigator.userAgent properties. However, using this approach again won’t solve the feature detection handicap mentioned above.

It would be both faster and more reliable to have the ability of using probing functions which can confirm the availability of objects, methods, attributes and so on (i.e. catering to the 4 points mentioned in the previous section)

We can always create these probing functions which then query for the required stuff, and if not found return null. But the overheads for these custom monitor functions increase if we are having a big web based project, intended to run on multitude browsers.

Enter the JavaScript library, Modernizr.