Google finds Java ‘portlet’
All the interesting things in Java are based on bytecode manipulation (erm.. instrumentation) – take Spring, Hibernate, AspectJ, Acegi security etc.
frameworks users prefer to modify classes in-memory, at runtime, based on non-standard configuration files, than to switch to a more modern language.
Now watch this: Google uses Java (hooray! – or, no, wait..) – and lately, Java is GPL (v2)
As Android came out, something happened:
Android‘s programs are written in Java, using Java-oriented IDEs (it also comes with an Eclipse plugin)… it just doesn’t compile the java code into java bytecode but (ops, Sun didn’t see this one coming) into Dalvik bytecode.
So my conclusion is that Google folks are better at re-inventing other’s ideas so that they shed a new light : a Java class is not portable, only the (open-)source is, and only the makers of Android can stick to binaries!