Hacker News Reader

"You can start using Java 8 as soon as you are willing to move."

As long as you aren't writing Java code on Android, in which case you're still stuck at Java 6 (with a very small subset of Java 7 features that were added 3 years after Java 7 came out).

Not the fault of the Java language, really, but it is incredibly annoying how unclear Google has been on the future of their dialect of Java post the Oracle lawsuit.

View on HN

I have been waiting for servlet 3.0 on App Engine since 2010

https://code.google.com/p/googleappengine/issues/detail?id=3...

The funny thing is that google's own GWT requires it now.

It's worth noting that Android 4.4 does support pretty much all JDK7 features (multicatch / try with resources / etc), finally. I've run into the occasional missing method from some of the newer class libraries, but nothing too serious.

Of course, if this is any indication it'll be several years before its safe to use even JDK7 features considering Android's update trends, let alone JDK8 ...

This has made me use C++ for my hobby graphics programming on Android instead.

The NDK has all the support I need, when coupled with something like Qt/SDL/openFramerworks and C++11 feels better than Google's Java fork.

you should consider using Scala on android. works really well for my projects.

Which scala android project are you using?

Reply on news.ycombinator.com