Suzaku, I absolutely agree. Which is why we use a Framework we call Papyrus EYE and do not develop with FLEX or AIR. We deploy automatically either to Flash, our QT based thick client, or to AJAX. We even think about doing a Java EYE version. Using our own Flash code and stying away from XML we were able to bypass the FLEX performance issues!

Our Papyrus EYE displays HTML in Flash. The source code and definitions that produces the EYE graphic components are accessible too. The point is that FLEX Is a poor implementation made by developers for developers without considering the enterprise environment and user.

BTW, content management IS NOT only about 'authoring' a document, and even if it would be the user should have the option to set it up to his preference.

Max J. Pucher, Chief Architect ISIS Papyrus

Duane, I fully understand where you are coming from and from that perspective the world as seen by a developer is whole. But how about seeing the world from the perspective of an executive or better from a user perspective?
You make it very clear that working with FLEX is pure and (not simple) coding with all connected problems, particularly the ones of documentation, library dependencies, coding styles and maintenance. That cannot be the future considering the dreaded anti-buzzword of agility. We finally need to give businesses the ability to define the GUI they need without requiring programmers.
This is why we chose to create a non-programming library of GUI objects that are life-cycle managed and assembled in our repository and are currently implemented in QT and Flash with Ajax on the way.
FLEX was obviously created by programmers without considering the needs of the business. I thus agree with Tony that Documentum and others chose to dazzle user with 'flashy' GUIs rather than doing something visionary. We should finally learn to put people first and not technology.