First it starts by Google playing cheap and doing a Microsoft move on Sun.<p>Before I get the usual Sun CEO approved it reply:<p><a href="http:&#x2F;&#x2F;nighthacks.com&#x2F;roller&#x2F;jag&#x2F;entry&#x2F;my_attitude_on_oracle_v" rel="nofollow">http:&#x2F;&#x2F;nighthacks.com&#x2F;roller&#x2F;jag&#x2F;entry&#x2F;my_attitude_on_oracle...</a><p>Second, at least on lambdas they could generate inner classes for older devices and update DEX format now that Dex is compiled AOT to native code. So only the compiler dex2aot would be required to be updated.<p>Currently there is zero public feedback on the new compiler chain (Jack &amp; Jill), but from the sources it appears it is Java 6.5 all the way.<p>They have some unit tests that appear to be related to Java 8, but no one knows what is their idea.<p>In a few years (by Java 10 timeframe), according to the actual roadmap which might still change, Java will have modules, a JNI replacement, reifeid generics, value types, new array type, GPGPU support, AOT compiler....<p>If nothing changes, assuming Android 4.4 devices will be gone, the only change will be from Java 6.5 to Java 7, if Android&#x27;s team attitude is to stay like it currently is.<p>But at least they spend time doing those stupid devbytes videos, doing continuous buggy releases of the support library and Google services.<p>Android Java is definitely the second coming of J++&#x2F;J#.