It's kida a moot point...
Posted Mar 29, 2011 22:34 UTC (Tue) by khim
In reply to: Somebody needs to open Android back up
Parent article: How Amazon could loosen Google's iron grip on Android (ars technica)
Had we demanded a more open process it would have made it a lot harder for them to do what they have done...
You did. Once, twice, thrice... The end result was... underwhelming. Great things are not created by bazaars. You can only create them using cathedral approach. Sure, once certain level of maturity is reached bazaar starts to work, but you can not use it to create something from scratch.
Dumping Java from a rebooted phone platform design would almost certainly pay dividends in the most important issue currently impacting mobile computing: battery life.
Sorry, but it's not a guarantee. All three aforementioned platforms used C/C++, not Java. All three had worse battery life then Android. Sure, it's possible to create less power-hungry platform then Android with Dalvik, but abandonment of Java by itself does not guarantee that.
Fork Android from the last code dump into a Git repo, forget 3.0 ever happened and move on.
Interesting idea. One question: who will fund this work? Volunteer-only effort may take literally years - and it's result will only be interesting to anyone if/when Google will never release future versions of Android.
I'm not saying everyone should accept the Google's game, but before you'll go and try to propose alternative make sure you have enough support behind your back to actually deliver this alternative. Better yet: have this alternative already available. Last time I've checked the whole famed "community" was unable to deliver even half-decent Flash player (because most were satisfied by zero-priced closed source alternative).
Don't overestimate the strength of the "community" - it's powerful, but it's not omnipotent... and it can be easily swayed by "good enough" alternative.
to post comments)