[michaelt]

The vast majority of projects, at my employer. I personally upgraded several hundred JVMs running several dozen services - upgrading was simple and almost entirely painless.

In addition to benefiting from the new features, being up-to-date is good for recruiting. You tell someone they'll be working with Java 6 and (in the absence of other evidence) they'll assume it's a legacy product suffering from chronic under-investment. Not exactly the impression you want to give job seekers!

[pjmlp]

> they'll assume it's a legacy product suffering from chronic under-investment.

Or Android.

[bitmapbrother]

Hopefully they'll ditch Java and go with a superior language.

[pjmlp]

I don't believe, given what they repeat at every Google IO when people ask about it.

Also I don't have any issue with Java as I do like the language and use it since JDK 1.0.1.

My issue is with Android Java, a forked version of Java with cherry picked features of Java 6, 7 and now 8, just because Google didn't want to pay Sun.

A version that will be even harder to write portable code when Java 9 and 10 come out.

[bitmapbrother]

Or perhaps they know better than to release confidential information about their roadmap?

I believe Google is running out of solutions to further optimize Android because they keep running into self inflicted Java roadblocks. If Fuchsia is any indication of their future efforts their next major overhaul will support multiple first class languages.

[pjmlp]

Check the bios of many of the major Android team leads, some of them were former Java developers at Sun, which I think has a big weight on Java's role on Android.

As for Fuchsia and Brillo, it remains to be seen if they will ever be productified.

Also I don't believe that Dart is a better option than Java in regards to performance.

[st3v3r]

Presumably they'd know that they applied for an Android job.