Running and Living

Every morning in Africa a gazelle wakes up. It knows it must move faster than the fastest lion or it will not survive. Every morning a lion wakes up and it knows it must move faster than the slowest gazelle or it will starve. It doesn't matter if you are the lion or the gazelle, when the sun comes up, you better be running." - Roger Bannister

Ayodhya and does it relates to common man ?

I saw this photo on News paper long back and finally got to from google. Today verdict of Ayodhya is coming up and its so tense here, partly made my media.
 

Here the muslim mother dressed up her Kid as Lord Krishna on the occasion of Krishna Janamashtami festival at school.

 

Common person has nothing to do with Ayodhya etc, what they need is good education, food security, social security, job opportunity and peace.

Android and the Sun's ignorance behind its success

Around 2002, when J2ME was at nascent stage and Motorola was at its peak, there were many projects inside the corporate as LinoJava and JavaLin. The idea was to develop full phone (Java Phone) which will have all the apps in Java or at that time J2ME (in mid of CLDC and CDC) running on embedded Linux, with full support from Sun. Years passed with many reviews, re-reviews and parallel multiple implementations.

In 2007, Android came, with a big push from Google (as usual they bought the technology). With Android came a big hype and tremendous support from OEMs. Seeing it closely, its nothing but Java Phone, which Moto and Sun thought of and never made it public. So what exactly they missed, I know I know much bureaucracy and impractical leadership are core reasons but I am trying to think of what technical steps they missed and Android Inc. did, a just 22 month old startup, headed by Andy Rubin who also co-founded Danger Inc. (now with Microsoft):

1/ JVM should have been redesigned with close association with threads and the kernel. Sun had solaris with excellent thread support from kernel, infact the first OS to realize the importance of threads. They did a bit to port the Solaris on x386 architecture and make it open, but never ever realized to make micro Solaris for smaller devices. Sun was just stuck with J2ME and generic implementation, never believed for extended support from platform, or never realized the need for full end to end platform support.
 

2/ A good post-processor which should have optimized class files more closely to fasten the execution. BlackBerry did this to generate COD files, and that makes the application near to native and so what Android followed. Sun kept class and jar format close to the heart, did not believe in to optimize more and kept it very rigid to the RFC. That may be because of the existing OEMs with J2ME implementation, forcing a reference HW platform could have been too harsh. Sun failed to see the need of it and J2ME was always seen as interpreted language, too naive for real phone application.
 

3/ Application store, the key stimulus for OEMs. Sun never gave this platform to any OEM, they were stranded to load the pre-apps or leave users to the mercy of websites with mobile apps. OEMs never gained the confidence to build a full device on Java, so spirally it affected Sun back to never think or push more on Java phone.
 

4/ Closed capsule in entire approach. Its well known and well accepted feature of J2ME to run the application in close capsule for good security. But it affected the entire J2ME to reach where Android is. For every new thing as File system etc, new JSRs were filed but they were like optional packages.

There are some more technical reasons as no application manager to check responsiveness or poor SDK to not to simulate the real conditions, but I feel above 4 were core to the android's success and J2ME's limitation to OEM devices but not the entire platform on which full device could be build.