Re: AOT.
At the JVMLS summit there was a talk on a HotSpot AOT compiler mode. It's
being worked on, however, as a commercial feature.
RoboVM provides an AOT compiler for iOS.
Not sure, I would suggest asking on the project proposal thread?
- Don
On 07/10/2015 5:25 PM, Richard Bair wrote:
Donald, do you know if the iOS version has the JIT compiler? I know Apple
reduced the restriction for some cases, but I can’t remember if it applied to
us or not. Or is the VM on
Donald, do you know if the iOS version has the JIT compiler? I know Apple
reduced the restriction for some cases, but I can’t remember if it applied to
us or not. Or is the VM on iOS interpreter only?
Richard
> On Oct 7, 2015, at 2:21 PM, Donald Smith wrote:
>
> There is no "official JDKs fo
JavaFX is already 100% open source. It can be used with the code that
will be contributed when the proposed OpenJDK project is approved.
These are not orthogonal in any way.
- Don
On 07/10/2015 5:21 PM, Felix Bembrick wrote:
What would be the reason/logic for not including JavaFX in these
What would be the reason/logic for not including JavaFX in these JDKs?
> On 8 Oct 2015, at 08:19, Steve Hannah wrote:
>
> I recall reading that these JDKs won't include any UI components. Since iOS
> doesn't support JIT, the iOS port of JDK will certainly be AOT compiling.
>
>> On Wed, Oct 7,
There is no "official JDKs for iOS and Android", and anyone that tries
to spin the recent OpenJDK project announcement as such is likely just
trying to consume you as click-bait. The recent project announcement is
simply to make internal code we have for some of our other commercial
products
I recall reading that these JDKs won't include any UI components. Since
iOS doesn't support JIT, the iOS port of JDK will certainly be AOT
compiling.
On Wed, Oct 7, 2015 at 2:11 PM, Felix Bembrick
wrote:
> The world of Java and JavaFX is growing more confusing than ever it seems.
>
> Some say O
The world of Java and JavaFX is growing more confusing than ever it seems.
Some say Oracle is cutting back on funding for Java because it is effectively
helping its competitors. Sounds similar to Google forking WebKit so they
weren't writing code for Apple.
But now we hear of the looming releas