What does this mean for the future of JavaFX on iOS?

[Johan Vos]

Comparing JavaFX and Xamarin doesn't really make sense.
JavaFX is a technology, Xamarin is (was) a company.

But looking at the eco-system, there are a number of differences:

1. JavaFX uses Java, Xamarin uses .NET. If you're a Java developer, JavaFX
should be your choice. If you're a .NET developer, Xamarin should be an
option.

2. JavaFX provides a cross-platform UI. While Xamarin has a product called
Xamarin Forms, the primary usage of Xamarin still implies creating a
separate UI for Android and for iOS (using different API's).

The whole point of JavaFX being a cross-platform *UI* framework is very
important. Write Once, Run Anywhere.

- Johan



Op di 19 apr. 2016 om 14:23 schreef Tobi <tobi at ultramixer.com>:

> The question is: How does perform JavaFX in comparison to e.g. Xamarian?
>
> > Am 19.04.2016 um 13:14 schrieb Scott Palmer <swpalmer at gmail.com>:
> >
> >
> >> On Apr 19, 2016, at 4:18 AM, Felix Bembrick <felix.bembrick at gmail.com>
> wrote:
> >
> >>
> >> Let's face it, without highly optimised AOT, Java and/or JavaFX on
> mobiles is simply not viable which in turn implies that JavaFX itself is
> not even worth looking at... RIP.
> >
> > Let's not go crazy. JavaFX is still the best bet for desktop apps.
> Despite all the hype desktop apps aren't going away. Browser-based apps and
> JavaScript are still garbage in comparison to what JavaFX offers.
> >
> >
> > Scott
>
>