Compared to the alternatives, Android is fantastic.
In my opinion that’s not so much because of Android in itself, but a phone is just a really different platform in all aspects. So even if Android would support a full fledged J2SE implementation, the effort in porting would not be so much different as it is now. Like I said, Android’s main culprit is the VM’s lack of performance.
Agreed, I haven’t found anything useful is actually missing from the libraries, it’s just that you quickly find you’re better off not using them (in your main loop) once you take a look at the allocation tracking tool. The GC is a hog.
Outside of the rendering loop, on the other hand, it’s all gravy.
It is quite easy to naively port a program to Android but it does not give the expected result in term of performance and handling several versions of the API is not trivial (the API version number is not available everywhere but the API version string is). For example, if you want to support multi-touch only where it is available, it becomes very tricky to implement, it requires a wrapper class:
http://blog.javia.org/android-application-backwards-compatibility/
Ideally, I would like to have only some specific source code for input handling and that’s all. Of course, I would use some models with less details on mobiles than on desktop computers.
Well that depends on your expectations, doesn’t it? 
Although I agree the Dalvik VM is not as fast as it should be, it’s not because dalvik is not J2SE.
That doesn’t look different than with J2SE, though?
Who said anything about Oracle killing off Java? You have to remember that there are two sides to this, Oracle and the people that use it.
So this could be a ‘suicide by cop’ kind of thing. Bad press et al can kill your product.
What Oracle wants is for J2ME to be on the phones, not Android/divawhatever. Maybe Oracle missed the memo but J2ME sucks and exactly the reason why Google made it.
As far as Oracle putting money back into Java … yeah, right. Put more money into it? Why? It works doesn’t it? Spending money on stuff to make lazy developers happy is not really a business case.
And you can bet what ever they do put into Java, won’t be done because it is ‘right’ but because there is a market value behind it (design by comity).
I don’t think so and I remind you that Dalvik uses a completely different approach in memory handling, it has nothing to do with J2SE.
Have a look at the links I provided, it illustrates my post.
I agree with James Gosling:
[quote]Java ME’s fragmentation was far worse than we would have liked. Some of it was politics in the early days, then 10 years later, small cracks in interoperability become gaping holes. A big factor was that the incredible constraints of the handsets 10 years ago made consistency almost impossible. Today’s high end phones have an incredible amount of RAM and CPU, which makes interoperability hugely easier for Android.
Fragmentation limits programmers freedom because it increases the amount of work that a developer has to do to address a large market, and the larger the market you can address, the better your chances are of being financially viable. So long as handset makers are “lazy” about implementing Android and don’t take advantage of the freedom they have to alter the Android source code much, life for developers can be good. But differences will creep in as the Android world ages: version skews, different bug fixes, and the handset makers attraction to “added value” and “product differentiation” will all take their toll without strict governance.
[/quote]
J2ME is crappy but J2SE Embedded is more scalable than Dalvik VM.
The Big G is right. It needs to be like Windows or iOS - ruled with an iron fist.
Cas 
Big G already do that. They have certification/compatibility program for Android, and if your device doesn’t pass it, its officially not an Android device.
Well, that’s good then. I hope their equivalent of the TCKs are stricter than J2MEs were 
Cas
I think you misunderstood my post. I never said anything about Dalvik’s memory handling being the same as J2SE.
I said “it’s (android’s bad performance) NOT because dalvik is NOT J2SE.”. 2 times NOT, see?
I did. It doesn’t look very different from how it works in J2SE though? (although I’d never use the 1st ‘version string’ solution)
The following is a quote from the official Oracle website:
I don’t think Java will just be hang and forgotten. It is a well known language and alot of people use it (just not for industry games…).
I, for one, supports Oracle against Google.
I have never been a better programmer since I started working on J2ME with just a Canvas and nothing else.
My java bytecode will work on J2SE Bridged from J2ME.
Can you bridged Dalvik code to J2SE?
I’m against branching the Java bytecode.
Google officially responds
http://www.osnews.com/story/23873/Google_Officially_Responds_to_Oracle_Android_Patent_Lawsuit
:-X
I’m really interested in what will happen, over the next months and years.
What’s everyone’s idea’s on the licensing for being able to sell the games or software you create with the tools provided?
eh that doesn’t matter too much but, what about the open source idea…
[quote] Oracle has been exposed for the anti-Freedom, anti-open source company that it really is.
[/quote]
what if it is made you have to pay licensing for the sdk? how do you think this would affect the community, better question - Who will leave java for good ? (unless of course it becomes open source again)
This is causing me to debate whether or not to start anything new in java …
my next project was set to start construction in mid November, We shall see what news in brought forth
You don’t actually need the Oracle JDK. Eclipse has it’s own compiler, and the JRE runs your apps just fine.
Oracle will have this brand new Office Suite soon, so it’s in their own interest not to charge money for the JRE.
Then again, Oracle is known for charging for everything.
i know but if the change the licensing eclipse may be asked to pay and being that it is open source it defeats the perpose.
i do know someone who used to work for sun, who is now part of Oracle. Perhaps i should consult him.
IMHO any requirements for license fees for Java will kill Java.
Short term you might get some revenue because many companies have the stuff they provide built upon this, but they will then switch ASAP.
Yeah I really don’t see them adding fees unless they want to kill the language.
Really that article just shows that Google admitting they are in the wrong and trying to make Oracle look like the evil one. Though I wonder what will happen next. Maybe Google will try to do a deal before it goes to trial because it seems they will loose.