Mike's statement "I am sure there are customers using it" has reminded me a 
thought I had about the 'survey' which I wanted to share...

Many members on this list have probably felt an impact on their livelihood as a 
result of the changes relating to Adobe's actions around Flex. My primary 
motivation in committing to work in my spare time on Apache Flex would be to 
help ensure the longevity of Flex and hence my livelihood (although I recognize 
and respect for some it may be more oriented towards hobby/interest/other).

Although the survey attempts to get to the bottom of feature priorities, I 
can't help feeling that we should be including parties other than this mailing 
list to take part in the survey. Although many of this list's participants 
including myself have an exposure to a subset of the corporate users 
requirements, does anyone have any ideas how we could ( and if we should ) be 
trying to include the high paying end customers in our surveys ? i.e. the big 
corporations that were (and in some cases are) spending money on Flex 
development ? Is this information Spoon can get access to through their network?

For example only, I personally can see a big benefit to putting effort into 
FalconJS, but it may be that 9 out 10 large spenders in Flex development may 
actually not care about HTML/JS and are more concerned about performance 
increases/additional components/bug fixes, etc ?

Obviously I appreciate that some of these large spending corporations will have 
members monitoring this list, but some may not as they probably relied on Adobe 
(and partners) sales & marketing effort to keep them posted. 

I am not saying I like the idea of a 'roadmap', but I do like the idea of a 
'picklist' of features that paying organizations have stated an interest in. 

As much as I appreciate the effort which has been put into the survey, I can't 
help feeling it is a little bit leaning towards some kind of 'progress report' 
on Adobe donations rather than a focus on whats next.


dan

Reply via email to