Open source Java for Android? Don't bet on it

Industry observers aren't optimistic, despite chatter about the possibility in OpenJDK circles

By , InfoWorld |  Software, Android, java

With Android, applications run on the Dalvik managed runtime. Android's environment is not compatible with Java even if it is similar, Sellers said, adding that Dalvik entails a learning curve. But he does not see Google being eager to move to OpenJDK. "Google doesn't have a vested interest in enabling a true Java environment for Android," he said. Sellers cites open source licensing differences as a part of the issue. OpenJDK leverages the GNU General Public License, in which any code changes or fixes must be contributed back to the community at large, a prospect not attractive to some commercial vendors, Sellers said. Dalvik abides by the Apache license, which does not have this problem, he notes.

Gosling: OpenJDK on Android could be doneThe possibility of OpenJDK on Android doesn't have any technical obstacles, Java founder James Gosling says: "Technically, it's not a huge problem. Android is just Linux on ARM, and there's already a nice ARM/Linux version of OpenJDK. There are issues that would make the current binaries inappropriate (mostly graphics integration), but it's not insurmountable." Major benefits would be performance and compatibility, Gosling says.

But Gosling too sees business obstacles: "The hard issues are business. Google and [mobile rival] Apple both want walled gardens, although Google is much less blatant than Apple."

One developer already has pursued the idea of accommodating Android on OpenJDK. "Some time ago, I started with some friends a project called IcedRobot, about porting the Android API on top of the standard OpenJDK," says Mario Torre, a senior software engineer at Red Hat, who stresses he is not speaking on behalf of the company. "The idea was that it would have been interesting to give Java developers the ability to use the Android framework.

"The obvious advantage is that you could keep running and supporting legacy applications, but at the same time benefit from new and more modern APIs, which are really widespread, well understood, and easy to use," Torre says. The project stalled, however. "The problem we had is that there is a very high entrance barrier, and since, at this early stage, the outcome for a possible adoption is still unclear, we didn't manage to attract a lot of developers." There was a lot of interest in the Daneel Dalvik-to-Java bytecode converter that was part of the project, he says.

Originally published on InfoWorld |  Click here to read the original story.
Join us:






Ask a Question