Of course, GOOG made a wrong decision with deciding on Java VM, to be used inside Android.
And now GOOG is paying the price. That is: they are about to pay, even if there is no money involved, and even if they do not loose in the court v.s. Java owner: Oracle.
Chrome OS on a Galaxy Mobile Device?
To mitigate all of this, what GOOG could do (realtively easily) is to release GO development environment and Run Time for Android. As a matter of fact they could make a “knee jerk” reaction and release more or less immediately, Chrome OS Mobile, for (almost) all relevant devices running Android today. But. Imagine what would happen if suddenly we would have Samsung GS2, GS3 or Nexus, with Chrome OS, or even “just” GO runtime environment.
But this is where this cardinal mistake comes to light so clearly. Alas, Android was released too soon.
2 thoughts on “Chrome OS on a Galaxy Mobile Device?”
What makes you think that they will come up with Chrome OS for android.
Wouldnt they choose some other open source mobile OS?
are already gearing up for the competition.
GOOG will not buy any new OS that much is for sure. GOOG have invested a lot in Chrome OS, GO prog. env. etc. Recently it was somewhat moot point where they will use this first. I think they can use, at least, the GO RT and dev env, to make Java less prominent on the Android. And especially to avoid further attacks from Oracle.