On Mon, Feb 8, 2010 at 10:19 AM, s <[email protected]> wrote:

> JavaFX?
> This is a great thread.  Having been manic on JavaFX coding for the
> past year myself, I must say that the language is a major game
> changer, which I feel is only realized after extensive development.
> It is a paradigm shifter especially in terms of design, and contrary
> to categorization, it only minimally seems to be a "scripting"
> language in my usage.  I find my projects and style have taken on the
> unique characteristics of self-organization and emergence, because
> trying to apply many of the old design and architecture rules do not
> apply to this unique phenomenon, which I call a phenomenon because it
> is too liquid to detail (yet).  I probably couldn't explain it even if
> I tried because at this point, you adapt to JavaFX, not the other way
> around.


I also have noticed that you have to think about things very differently.
 But the great thing is that implicit binding and the scene graph can let
you do things that were just so painful other ways.  I really like the
potential.

However.  If you are trying to write an interface to existing code, the lack
of generics is painful.  The lack of arrays or easy access to Java arrays is
also painful in some situations.  Sequences are interesting, but they just
don't do it all.  It just doesn't feel like a "heavy lifting" language yet.
 It feels hard to write robust solutions to more complex problems.  (I
understand that it is still evolving, but I feel it still has a ways to go.)

Also, I'm not a fan of the distribution model.  It seems that the
tools/licence won't let you make an executable jar and just send it out. (If
you try you get main class not found)  For internal enterprise apps, is it
realistic to only use JNLP?   If you try to actually run an app outside of
the IDE, wow, it is painful.  I can see how just that experience alone would
make a novice programmer give it up for good.  For example, for any target
platfom with a JRE less than the most recent, you have to open some files
generated by the IDE and hardcode the website of the hosting site.  (Oh, and
they don't really tell you any of this, you have to go google it up
yourself.) (Oh, and if you do have a config issue or crash with an applet,
the java console will show you the error if you know where to look, but the
nifty little javascript loader just keeps telling you that it is loading, no
error message.)

I would love to see how long it would take a some without any JavaFX or JNLP
experience to download the tools, build hello world and publish it.  For a
product that is supposedly targeted at a larger audience than core
developers, I was surprised at the steepness of the learning curve.

I'm really hoping that this all works out eventually.  I really do like it.

Have you had any problems with these issues?


> This language is a God send.  I've given up all else.  Java
> is nothing but an interface language to me, now.  I may be shooting
> myself by doing this, but I'm all in.  As for Swing, no need to touch
> it, even now without 1.3; the alternatives combined with creativity
> are too precipitous.
>
> Steve Sobczak
>
> --
> 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]<javaposse%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/javaposse?hl=en.
>
>

-- 
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.

Reply via email to