JavaFX will be filling a recess/alcove/niche, where no other product will successfully be. Have a look at Flash and Flex, which wants also to run on that different systems. But Flash is disigned for videos and so, but not for widgets. With Flex you can create widgets (surprisingly the Flex-compiler is written in Java), but it still runs on Flash. To write widgets for a platform like flash isn't a problem for a big company like Adobe. You can on every platform - where you can program, that on point x,y will be a pixel with color c - lines, circles, rects, gradients, buttons and so on. But important is, what supports the platform (Flash). Flash can not create new windows. So if you have a tooltip, with Flash it is possible, that you can't see it, because a part of the Flash-video is scrolled down in the browser. Java on the other side, creates a little new window without frame, where the Tooltip stands. And Java know, where the Applet/Application on the desktop is. Also important of an good platform/VM is, how many devices it supports, If you have in Flex a scrollbar written. You can not scrolling down with your mouse-wheel, because it is not supported by Flash. The same with the middle mouse-button. And the right mouse button mostly show a "About Adobe Flash Player XX". So you have for *.swf programs mostly only one mouse-button which can be used in your program, Java and JavaFX supports all of the mouse. To find fans of Flex, Flex was extended with lot of effects, which gives a nice look and feel. Silverlight on the other side, is written by Mycrosoft and exist only for Windows and MacOSX. For Linux existing Moonlight, which is OpenSource, but Moonlight is only an implementation of Silverlight. So, the Original isn't OpenSource and it runs only on two Operating Systems. So, JavaFX is the only one in that area, to support disigners and developer. JavaFX (pronounced "Java Effects"), gives Java the nice effects. And it seems, that Sun is in hurry to come out with JavaFX. The goal is, that in the end, JavaFX will be completley OpenSource as OpenJFX, as Java is OpenSource as OpenJDK. But to have before something to publish, the current JavaFX Script isn't OpenSource, because it includes Third-Party code. And in the videos of www.JavaFX.org are a JavaFX puiblished, where Sun not even have the right to publish it free of charge. But Sun thinks, that instead publishig JavaFX in year N completly as OpenSource, it would be better to publish it in year M at first free of charge, and making it later OpenSource, so that is then in year N OpenSource. Also they think, that instead publishing JavaFX in year M completly free of charge, it would be better, to present beforein year L videos of a JavaFX version, which they can not publish at the current time. But which shows the way, where it will go. And later when most parts of it are rewritten by Sun, it will be in year M published free of charge and in year N as OpenSource. Hopefully I haven't mistakable worded.

Actually i read JavaFX every 2 Days there. Nothing interresing to read at all. Actually i think there should be the Focus on Update 10, nothing else! What makes my annoying is the Fact that i seems that i have to use FX to use upcoming Media Components. Please wake up at SUN.

Actually i read JavaFX every 2 Days there. Nothing interresing to read at all. Actually i think there should be the Focus on Update 10, nothing else! What makes my annoying is the Fact that i seems that i have to use FX to use upcoming Media Components. Please wake up at SUN.

JavaFX is just another example of the "ME 2!!!!!" attitude pervading everything Sun has been doing for the last few years.

JavaFX is the most important new part to the Java environment. For years, Java has been more of a backend solution than a TOTAL solution. Sure, we could write great backends, but then we had to rely on JavaScript/AJAX/Flash for the frontend. That lack of depth for Java gave opportunities for Flex and SilverLight to grow. So why should we care? Why not write our backends in Java and our frontends in AJAX or Flash? Two reasons: 1. Completeness. Wouldn't it be better to have a solution that is Java from top to bottom? JavaFX is just a syntactic wrapper over Java. Break the surface and you're in Java, and you can integrate your Java code directly into JavaFX and vice versa. 2. Encroachment. Flex is starting at the UI level, but it won't stop there. To support the UI they'll continue growing downward into the backend. Why be content to let that happen? Java is in the lead, why not shut them out? More importantly, SilverLight is already built on top of the .Net code base, so they've already got a solid solution, and we've seen that M$ would like nothing better than to kill Java. So why is JavaFX the most important NEW part of the Java environment? Because without it, competing technologies have a better chance of displacing Java. And that's not good for any of us.

... but it seems like everytime I go to use it, it's different (not backward compatible) from last time and/or requires a new buggy build of Netbeans to use. Until it's available as a working plugin to a current production version of Netbeans, I can't see me spenind too much time and effort on it. I hear that we'll see that by the end of the month... hopefully, Netbeans won't have moved to 6.2 by then with JavaFX being incompatible with that.

To me Java FX seems like teen. Looks talented but at same time confusing. Looking promising but at same time vulnerable. Will grow anyway but not sure with what personality. In one sentence: Lot depends on good parenting and care.

.I personally and professionally have no need for what JavaFX offers. More so, it's not clear what it's real direction is so I have little or not interest in learning it either. I suspect it's going to become the next JMF...never fully baked and completely abandoned.