Yeah while I too can also appreciate the theoretical advantages of Flex/Silverlight/JavaFX, they will always be containers and limited by their own hacks to interact with "the native web". Every time I see a JavaFX demo and the use of the (deprecated 10 years ago) applet tag, I laugh a little to my self. For the current web, GWT and jQuery wins. It runs anywhere, there's no deployment, development round trip time is minimal etc. Testing can be tricky however. But considering how browser vendors continue to push the limit it's hard to imagine this trend reversing (I.e. Opera's Carakan engine now makes Chrome look like an old version of MSIE: http://lifehacker.com/5432054/opera-105-pre+alpha-is-all-about-speed-and-private-browsing).
/Casper On Dec 22, 5:20 pm, Mark Volkmann <[email protected]> wrote: > My feeling is that jQuery makes up for a large number of the > deficiencies. I won't claim it matches Flex, but it is very nice. > > On Tue, Dec 22, 2009 at 8:55 AM, [email protected] > > > > <[email protected]> wrote: > > >> I'd really like to hear more about why you feel using > >> HTTP/HTML/JavaScript is wrong and can't provide an elegant > >> solution for certain problems. Can you elaborate? > > > (I know that this is highly controversial and partly > > subjective). > > > Because the web has not been originally designed for web > > applications and the whole history of AJAX is the history of > > a set of hacks. For years, AJAX has just pursued things such > > as drag-and-drop, that had been state-of-the-art in the > > desktop for years. The average usability of an AJAX > > application is still behind the one of a regular desktop > > application of a few years ago and I weekly scream, while > > using a web application made by others, because of a form > > data loss or such (due to a temporary disconnection or a > > back button) - or more subtle things such as a total break > > of the application because it failed to completely download > > some script. > > > Of course one might argue that it's not AJAX fault, but a > > fault of most of AJAX developers (but when it comes to Swing > > and the many things that it did wrong in the past, the blame > > was with Swing, not developers). > > > On the contrary, my experience with Flex applications (just > > to cite the most spread technology) is completely different > > (e.g. Parley's rich client). Unfortunately AJAX and the > > other stuff is there and won't go away, so we have to deal > > with it. > > -- > R. Mark Volkmann > Object Computing, Inc. -- 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.
