They would merge the Flex team and the Flash player team, and
truely support things like MXML in the player. Why in the
world do you need 2 entirely different ways to build
applications in Flash? Why doesn't the Flash player itself
understand Flex MXML? Why must Adobe's resources be split
trying to build, promote, support, and refine two entirely
different experiences for application developers? IMO,
collapsing the teams into a single team would be the way to go
with the introduction of Silverlight, especially considering
that just about everyone on the Adobe side touts Flex as the
real competitor to Silverlight, not the Flash IDE... yet all
the big bucks are behind Flash, not Flex. It seems to be a
given that the Flash IDE itself is needlessly complex and
horribly inefficient when trying to do anything other than
animation. With the push away from animation to more useful
tasks, how can Adobe be missing this important step?
2 Comments
Simple. Availability. Flex 3-4 are committed to run
under Flash 9. That's the next 3 years.
Why? Because Flex wants a stable install base. Flex is
about application development not about fancy new stuff.
Flex has all it needs from Flash 9. The only thing it's
missing is the 98% installed everywhere badge.
Had you ever used Flex you'd know that MXML is compiled
down to AS3 code. In fact, MXML and ActionScript is one
and the same thing. The Flash Player understands that
pretty well...
I recommend you take a closer look at Flex before
posting this sort of stuff.