>From the perspective of an ISV, here are a few thoughts for the experts:
1. Question: What are the key ingredients to allow Flex to thrive in its new environment? Which technology is a similar, successful example, and how is Flex going to imitate this example? 2. Comment: someone questioned Tour de Flex as being useful or not, and I would vote that it has been extremely useful in understanding what can be done, as part of the decision-making process of adopting this technology versus another. It is one of your main customer-facing accomplishments and should be kept fresh. 3. Suggestion: If the percentage of Flex enterprise-application adopters is high enough to justify this, I would recommend the list consider including lots of examples and topics related to connecting to the back-end (e.g. Java/Spring)…this is where the data resides, and many times this is where the critical data resides for a business. 4. [Let me know if this is too off-topic] Compete with HTML5, and win (choose your battlegrounds, though). What are the natural advantages (leverage) inherent in Flex that are differentiators, enough to keep far ahead enough to keep your adoption rate at an acceptable level? 5. Question: does HTML5 ‘websocket’ compete with BlazeDS? 6. Does the Spoon Project overlap Apache’s role significantly? Thanks. Eugene (First time poster, looking to contribute)
