The competition

[Pedro Duque Vieira]

Hi,

I agree with practically everything Daniel said.

I've previously stated that deployment is seriously jeopardizing the
adoptance of JavaFX. Let me give 3 use-cases I've experienced in which
JavaFX wasn't a choice because of this:
1- An hobby project of mine (called Modellus) in which students and
teachers can create simulations of math phenomenon. Animation, charts,
tables, etc can than be used to better illustrate this. I'm still using
JavaFX here but some features will not be possible because of this.
*The problem*: Users want to share their models (Modellus files) on the
internet via a web site with other users. They don't want this to require
other users to download and install Modellus, at least not in a explicit way
*The possible solution*: If applets were working this could be feasible.
2- A wallpaper (as in for actual walls) internet shop wants to provide a
service to their customers in which they can create their own custom
wallpapers. For this, customers can upload images and assemble them in the
way they want.
*The problem*: Ideally this should require zero install and zero hassle for
the customers. The zero install part is not possible with javafx. HTML5
might be the solution however if at all possible one would face serious
technical difficulties.
*The possible solution*: If applets were working this could be feasible.
3- A Content Management System for mobile phones (initially android and
iphone). Through a site an administrator manages the content that should
appear in a mobile phone app.
*The problem*: JavaFX isn't available for mobile phones. The client has
decided to use phone gap for this, however development with this technology
is sub optimal and performance is also an issue.
*The solution*: Have JavaFX run on mobile phones.

Thanks for your time, cheers,

-- 
Pedro Duque Vieira