to include in future versions of our products -- but the positive reaction to reverse debugging certainly helped us with prioritization Many of the Flex SDK components like HTMLControl rely on internals of the Flash/AIR Player which are not open to the community. How would community development at Apache handle the same? People would only be able to build new controls and wrappers over what is available, right? Will Adobe accept the Flex@Apache proposals to add more features to Flash/AIR runtimes which they would need to develop more advanced features? Development on "Monocle" continues and is unaffected by recent announcements. We don't openly discuss product team sizes -- the team of engineers working on the open source contributions to Flex SDK is a subset of the existing Flex team. Open source Flex SDK development can continue against released versions of the Flash Player and Adobe AIR runtimes. In terms of roadmap -- we didn't previously communicate a timeframe for future enhancements to Flex. With significant contributions from the community, it is entirely possible that development will continue at an accelerated pace. Lastly, I have been using JetBrains IDEA as well as Flex Builder, and find it far superior in many areas eg. refactoring really works, unused variables appear grey, "find usages" really works, safe delete of classes checks for references and removes from version control etc. Could you set up a formal agreement with them and move FB-unique features into IDEA ? We would get a superior IDE and you