Search |
||
How quickly will JavaFX be adopted as a rich client technology?It's growth will be explosive
4% (27 votes)
Eventually it will be a dominant technology
13% (79 votes)
It will endure as a secondary option
22% (139 votes)
It will never be widely used
53% (325 votes)
What's JavaFX?
4% (24 votes)
I don't know; other
4% (25 votes)
Total votes: 619
»
|
||
|
|
Not what I expected
- you have to deploy using web technology (WebStart or Applets) and cannot just hand out a file
- the language seems to be thrown together on a whim and does not cater to the Java-savvy (optional semicolons and keywords like "insert... into..." & "delete... from..." when methods would have done the trick nicely, completely different notation for function parameters and return types, constants and variable declarations - don't get me started)
- generated Java code is horrible to debug (lots of anonymous inner classes)
- there are no good development tools yet
- GUI layouting is still very inflexible
- the dependencies between your object instances remain vague, and even more so towards system-managed objects like the Stage
- the documentation still is lacking for language featues - see "at" and "tween", for example
I think that there is still a lot of work to be done on JavaFX and that there is quite some potential, but some design decision that were already made have actually turned me off.Not enough components...
Not enough components...
Depends
Depends