Thinking in programming

Things I like to talk about programming

JavaFX, why?

with 6 comments

It’s not a secret that for a developer is a dream to be able to build an application, and without modify it, run it in the computer, in the cellphone, in the TV, in the car, in all the screens of the life.

However, why to create a new platform for this?: The main disadvantage of the languages with a high level of dissemination and longevity such as Java, is that these same qualities requires a strong backwards compatibility, which in turn limits its ability to evolve.

JavaFX was precisely designed to meet these demands, while provide a new and modern language, RIAs, developer-designer work flow in mind, multimedia, Swing 2.0, amazing Flash’s style animations, and all this without leaving Java! Version 1.0 has been focused on providing a very good support to work with animations, graphics and multimedia. In other words, has been created a very strong base on which to add graphics controls, business applications frameworks, and so on.

For some, JavaFX is coming too late, for others, this is just the beginning of a platform with a great potential. The first step was solid, from now on everything depends on Sun supports to this promising platform.


Written by roger.padilla

January 13, 2009 at 17:33

Posted in Java Swing, JavaFX

Tagged with ,

6 Responses

Subscribe to comments with RSS.

  1. Sorry, I strongly disagree. Most of the good stuff in JavaFX is the media and scenegraph API, not the language itself. A few months of hardcore enhancements to Java instead (e.g. proper properties / databinding / closures) and we could have done the same in Java instead of forcing a new language down everybody’s throat.

    JavaFX (the language, not the API) is a colossal waste of critically needed resources that should have been put into enhancing Java itself and keeping it up to date vs. its competitors.

    Sun really blew it on this one. And the lack of enthusiasm for JavaFX is proof that most folks would have preferred core Java to be enhanced instead.


    January 14, 2009 at 14:17

  2. Jacek, you’re so right. The messages are clear: “Don’t complain, you’ve got Painters in Swing. Now go and maintain it yourself.”

    The real fight is for saving UI in Java. Not putting closures can be understood, even if there’s time to fix (in BGGA) the issues that Joshua Bloch pointed, even if he doesn’t want it fixed, he prefers his solution.
    But…no properties ! It’s clearly to attract developers to JavaFX, which is elegant and all, but some don’t want/need it !

    Now, I don’t think that JavaFX will be a failure. My last hope is JDK 8 (or a “temporary” fork).

    The next episode will be when they release their new UI components for JavaFX. We’ll see if it’s usable in Java, even if it will be less nice, less cool, less…
    I wouldn’t mind seeing a line counting comparison. All I want is keep coding in Java.

    Olivier Allouch

    Olivier Allouch

    January 14, 2009 at 15:45

  3. I disagree, from time to time something new have to come along, and although the future of javafx is uncertain, the initiative of sun is correct, fix java eventually would be too problematic, do you think that c# is the right path to take in the innovations filed? give it a couple of years and you’ll see…

    Oziel Jose

    January 14, 2009 at 16:46


    I am busy working on an all-Java alternative 🙂


    January 14, 2009 at 17:50

  5. Unfortunately, the things always happens step by step. I think any language (even C#), has left the ring with a full IDE support. Sun has started correctly bet by providing support from NetBeans, which as its time, is beginning to leave behind it to Eclipse in almost all areas.

    The main strength of JavaFX is the speed and the naturalness (in an ideal combination) with it lets you create and maintain the projects you created with, whether GUIs, animations, graphics, and so on, even a mixture of all. So, its main strength is the speed you get by use it.


    January 14, 2009 at 19:06

  6. I resume it: JavaFX (TheLanguage) = Ideal combination of agility and naturalness.

    Sure, you can can obtain with others languages the same result which you get with JavaFX. The question is, would you obtain it with the same levels of agility and naturalness?


    January 14, 2009 at 21:12

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: