What is the logic that says this product is good for J2EE but not Coldfusion?
It's not that it's good for J2EE but not Coldfusion, it's that Flex would be most useful to J2EE style development teams.

Obviously their largest projected market segment for Flex is J2EE development teams, so you'd expect their *first public presentation* of this technology to be slanted towards J2EE.

The idea is that Flex can be used as the view layer of a web application. Most J2EE development has a good separation of the view layer allowing them to integrate Flex into their development process *relatively* easily.

In contrast to J2EE, how many Coldfusion developers take, at least, an MVC approach to their web application architecture?

I'm sure somebody will find a good use for Flex in Coldfusion development, but don't count on Macromedia putting in the hard yards to sell it to CFers, because there's A LOT more money to make in the J2EE world than in the CF world.

I wouldn't mind being in the Flex training market if the technology catches on!

- tim

Mark Stanton spoke the following wise words on 18/11/2003 5:48 PM EST:
In response to some of the other posts in this thread, Flex is mostly of
interest to J2EE developers, not necessarily the typical cfaussie reader.
    
I've noticed this in the materials - any idea why? IE. What is the logic
that says this product is good for J2EE but not Coldfusion?

Cheers

Mark
  
---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004

Reply via email to