Hi, I haven't posted before (more of a lurker) however I am a log time user of Flex and I may be slightly off topic here, but I think it applies (specifically to the idea of forking). Here we make hardware and needed some way to display the information, we started using Flash around 2004, because it was a quick way to develop a display to view the information to multiple concurrent users without much fuss. Around 2007 we started transitioning some of our controls to Flex because MXML/AS was a better model for us then Flash, now everything we have is Flex based. Last year we decided to transition to AIR for 4 reasons:
1. We needed to have more of a mobile presence. 2. Loading and updating app’s is not much of a concern anymore. 3. We could use the existing codebase to accomplish #1, while still using it on our core area, the Desktop 4. If we needed/wanted to go back or add browser based stuff we could use FlexJS to help with that. With the idea of forking it feels like the output is taking precedence over the language, i.e. the transpiled JS is more important than the compiler. To me the best feature of Flex was that I did not have to worry about how to get somewhere. As to the original question, I feel the strongest point of FlexJS is the freedom to not care about JS. Probably not the best for marketing. -- Sent from: http://apache-flex-users.2333346.n4.nabble.com/
