Compared with Silverlight, it's been my experience as a programmer that JavaFX is more elegant and you can generally get the same job done with less code and simpler code. I also dislike Silverlight's heavy dependency on IDE-generated code. I've hit several occasions where I get a compiler error in tool-generated code or a runtime exception there, and it's extra frustrating to find the root cause of those issues. JavaFX doesn't usually need tool-generated code at all (the composer does, but that's completely optional).
The killer disappointment for JavaFX is the browser runtime. As mentioned above, page scrolling is wonky, you often can't close a tab with a JavaFX applet trying to load, the media playback is buggy, and on my Ubuntu 10.04 machine with the Sun JDK 1.6.20 set up, I can't get a single JavaFX applet to work (I get the loading animation indefinitely). The other issue is that JavaFX is a better Swing, but that is such a narrow niche. All client GUIs need to be in HTML/JS or maybe Flash or maybe in a smartphone native toolkit. The amount of projects were Swing or JavaFX is appropriate is very slim. Still, I appreciate JavaFX for what it excels at. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
