My thoughts on the question "So, why should we switch from Flex to JavaFX?"
is 'Don't do it, not yet - and maybe in some circumstances, not ever' I'm very much in favor of JavaFX - I've been working with it constantly since the 1.0 release, I think it has alot of potential, and it's allowed me to do things in Java on the client site I've never, ever been able to do previously. But it's not enterprise ready (yet) and a lot of the points you raise, are in my opinion are correct, I could get into the 'its coming, it's promised, you don't need it, JFX is 1.1' refuting, but that's probably fairly pointless. RIA and rich media supporting tech is not a zero sum game, I think there is room out there for JavaFX, and Flex and Javascript/HTML to co- exist, and if the JavaFX vision is delivered on across mobiles, desktops and TV, then I think it's going to be a worth while thing that will benefit Sun and the developers/companies who support it. But for now, given your circumstances, my advice is don't switch your company over - but play with it yourself, give it a go, watch how it grows up over the next 12 months, and avoid, like some people, piling on the hate when it has its inevitable stumbles. Diversity helps everybody - if any alternative technology was halted 'because you can already do that in x' we'd never have any innovation and progress. Two questions I have for you though, since I evaluated Flex early last year and decided to go with Ext-GWT for a major project: 1. Have you had any issues with .swf size getting out of control? 2. Does the flex runtime scale okay with a complex client? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
