A plan to bring Java to iOS

try {
threshold : 0, // You can set threshold on how close to the edge ad should come before it is loaded. Default is 0 (when it is visible).
forceLoad : false, // Ad is loaded even if not visible. Default is false.
onLoad : false, // Callback function on call ad loading
onComplete : false, // Callback function when load is loaded
timeout : 1500, // Timeout ad load
debug : false, // For debug use : draw colors border depends on load status
xray : false // For debug use : display a complete page view with ad placements
}) ;
catch (exception){
console.log(“error loading lazyload_ad ” + exception);

A proposal floating in the OpenJDK community seeks to jumpstart Java on Apple’s iOS. The plan involves restarting work on the OpenJDK Mobile project, which is intended to build the OpenJDK classes and API for iOS and Android, said Johan Vos, CTO at mobile developer Gluon.

Vos recently posted a . OpenJDK Mobile centers on providing the same APIs in the latest version of the OpenJDK source repository to iOS and Android, leveraging tools familiar to Java developers. The first focus, though, is on iOS, which has lacked traditional support for Java. Apple has not allowed the to run on the platform.

The new plan for OpenJDK Mobile would entail using the GraalVM ahead-of-time compiler to compile code at build time. (Vos noted that just-in-time compilation is not an option on iOS.) Compiled Java code could then be linked with native libraries compiled for the target operating system to create executables. This already has been done for . Using the GraalVM Native Images and OpenJDK classes, developers can create applications that follow Apple rules. Java developers would not have to learn Objective-C or Swift to write software for iOS.

“While Java may be late in the game on mobile, the fact that it is cross-platform, created with security as a key cornerstone, and that it allows for secure connectivity with cloud services, make it a real serious language for mobile development,” Vos said.

Java has been used for Android development from the beginning. However, Android is not -compliant and requires its own development tool – – and procedures, Vos said. Many developers face serious issues using Java projects and libraries on Android, he said.

Also part of the plan is a synchronized fork of the OpenJDK master, which would be created using . A Skara-based repository would be leveraged to build OpenJDK for iOS and Android.

 and the now-defunct .