Should JavaFX be put down?

One of (several) things I'm cranky about on this blog is JavaFX. Last December I asked if anyone knew of honest-to-goodness production JavaFX apps in the wild; in particular, as I emphasized in a later post, I wanted to know about JavaFX ads that run within a browser windows, as do most apps written in Flash and Silverlight (the technologies against which JavaFX ostensibly competes). And this February has at last brought us an example, and a particularly high-profile one at that: an interactive map on the Vancouver Olympics site that shows how many medals different countries have won over the years. The app is decently slick, though on my relatively up-to-date OS X laptop it took a longer than one might have liked to load.

But is it too little, too late? That's the verdict from the Register's Matt Stephens. His article has that snarky, dismissive tone that is pretty much required for the publication, but he calls himself a "Java fanboi" and seems to be talking more in sorrow than in anger. His suggestion is that Oracle ought to be killing the project, salvaging what's useful out of JavaFX and adding it to the neglected Swing, and integrating one of the JVM scripting languages to make development easier.

Not everyone is so negative, but even the boosters have their wish lists (including, uh, cross-compilation to iPhone OS). Doubters might want to check out Hinkmond Wong's longish presentation on JavaFX Mobile (be warned, the video begins with some totally loud and extreme heavy metal music for no reason I can fathom). I'd love to hear your take on whether this is a tech that Oracle should continue to invest in.