Take Flex for a Java test drive

by Steve Anglin

Christophe Coenraets posts this: 30 Minutes Flex Test-Drive for Java Developers. "The objective of this test-drive is to give you, in a very short amount of time, an understanding of how Flex works and what it can do. This test-drive consists of a series of samples kept as concise as possible (typically between 10 and 50 lines of code) to clearly expose features of interest. The samples focus primarily on using Flex with a Java back-end. The intended audience is Java developers with no prior knowledge of Flex."

Do you think Flex and/or Flash will be big for Java developers; and are you using it? If not, are you considering?



2 Comments

Adam Taft
2006-09-11 14:05:29
Flex is proprietary and has only one vendor. Java is moving more and more towards open and has multiple vendors offering products and services.


Flex is, for all practical purposes, stuck inside the web browser (for the client experience). Java w/ WebStart is more positioned for a true stand-alone rich internet application environment.


Flex is a short term deal somewhat riding on the "Web 2.0" frenzy. Java will still be here and more useful than ever in the future.


Why choose Flex then? I don't know, but I assume it has to do with a) the "coolness" factor of the flash gui, b) because it has a strong backing company. I can't see very many Java developers really caring too much about Flex. Though, I'm sure the PHB's think differently, which will force developers to use it. Too bad.

Stu Thompson
2006-09-14 06:15:18
I just happen to be a Java developer writing Flash-remoting code. Our Flash clients (in the browser and in a Windows wrapper) ActionScript 2 code accesses my server side code via AMF and HTTP.


We are about to start a new UI development effort with Flex 2...so this is all very interesting to me. My initial research suggests that ActionScript 3, which comes with Flex 2, will allow closer data type binding. That is something I am excited about. The Flex 2 Builder also looks to dramatically increase our UI guy's productivity...along with lots of new and sexy UI components. The only catch is the client side Flash 9 player requirement. (Flash 7+ is almost universal.)


We begin full time research and prototyping next week. I am excited.


"Flex is a short term deal." There are legions of Flash developers loyal to Adobe out there and are moving their way towards Flex. They are not going to disappear or retrain in Java. The first version of Flex was released over two years ago. Adobe, IMHO, has done a very good job of stewarding client side Flash as the way to provide rich multimedia client experiences over the web. There is no reason to think they'd muck it up anytime soon allowing a competing, open approach (read Java) to replace it.


(This all ties in with the "why is Flash more popular than Java in the browser" debate. My read is that a) Flash is more prevalent than Java on the client side, b) it is relatively easy-peasy for a UI developer to whip up something pretty for Flash players, and c) "web designers" (and other non hard core programmers) have been making many presentation technology decisions for *years*...and choosing Flash.)


"Flex is proprietary and has only one vendor." Proprietary, yes. But there are more vendors coming out. Check out http://www.osflash.org/ . Of them my company is specifically interested in Red5, an open source Flash server. The project is one year and the future looks bright.


So, Steve, I think Flex has a future and increasing numbers of us server-side java coders will be writing services for client side Flash.


Stu