JavaFX and the new Java 8 release schedule

[Richard Bair]

I don't know, so far there as been almost no traction with Win8 Metro-only devices and Windows 8 in general is getting very poor adoption. I'd say, the fact that we aren't yet on iOS and Android is a far bigger problem than the fact we're not on Metro :-). That said, we're (almost) completely open source so anybody who wants to step up and do a port… :-)

On Apr 19, 2013, at 9:42 AM, Ali Ebrahimi <ali.ebrahimi1781 at gmail.com> wrote:

> But, don't you think waiting for win8 metro support until 2016 (javafx 9) wouldn't be good for javafx adabtation? when people play with windows 12<330.gif>
> 
> 
> On Fri, Apr 19, 2013 at 8:55 PM, Richard Bair <richard.bair at oracle.com> wrote:
> Hi Ali,
> 
> No, as Mark mentioned on his blog, we're not going to add new functionality due to the slip, which would only cause it to slip further. The slip is due to not having enough bandwidth for all the tasks at hand, and adding more work just makes that even less feasible.
> 
> Richard
> 
> On Apr 19, 2013, at 9:24 AM, Ali Ebrahimi <ali.ebrahimi1781 at gmail.com> wrote:
> 
>> Hi Richard,
>> Is not achievable win8 metro support with this delay?
>> 
>> Ali Ebrahimi
>> 
>> 
>> On Fri, Apr 19, 2013 at 8:46 PM, Richard Bair <richard.bair at oracle.com> wrote:
>> > On a slight tangent, how has this security push affected the schedule of
>> > releases OpenJFX?  Can an accurate estimate even be made? (i.e.estimates of
>> > available engineering hours for OpenJFX cannot be reliably be made because
>> > of security work).
>> 
>> We don't give headcount or those sorts of things even to people under NDA, so I can't really give an estimate. However as Mark mentioned on his blog (http://mreinhold.org/blog/secure-the-train):
>> 
>> > Maintaining the security of the Java Platform always takes priority over developing new features, and so these efforts have inevitably taken engineers away from working on Java 8.
>> 
>> 
>> And this is definitely true of OpenJFX as well.
>> 
>> > IIRC There are still a few more components left to open source before it
>> > can be stood up entirely on it's own inside OpenJDK.  OpenJFX inside
>> > OpenJDK at least provides another distribution alternative besides "wait
>> > for next year."
>> 
>> That is a terrific point. Once OpenJFX can be built based on open code entirely, then you can build an OpenJDK + OpenJFX and use it without having to wait for 8. Of course you take on the risk that the pre-released APIs etc will change, but since going this route necessarily implies you are co-bundling, that should be a relatively easy risk to assess.
>> 
>> Richard
>> 
> 
>